(Urgent!) [docs][analyzer] Add documentation for alpha.fuchsia.Lock and alpha.core.C11Lock

[Szelethus]

Summary

Exactly what it says on the tin! Needed an extra label for the CTU stuff for the release notes, I figured its okay to land that under the same roof.

[Szelethus]

We will need to push this to the 11.0.0. release branch as well, sorry for the trouble.

[martong]

clang/docs/analyzer/user-docs/CrossTranslationUnit.rst

213

While we are here, could you please fix the typo we have here? analyer-config -> analyzer-config (the z is missing).

[hans]

lgtm please commit so this makes it into the release.

clang/docs/analyzer/checkers.rst

 
  void test() {
    BOOL b = -1; // warn
  }
 
 alpha.core
 ^^^^^^^^^^
 
+.. _alpha-core-C11Lock:
+
+alpha.core.C11Lock
+""""""""""""""""""
+Similarly to :ref:`alpha.unix.PthreadLock <alpha-unix-PthreadLock>`, checks for
+the locking/unlocking of ``mtx_t`` mutexes.
+
+.. code-block:: cpp
+
+ mtx_t mtx1;
+
+ void bad1(void)
+ {
+   mtx_lock(&mtx1);
+   mtx_lock(&mtx1); // warn: This lock has already been acquired
+ }
+
 .. _alpha-core-CallAndMessageUnInitRefArg:
 
 alpha.core.CallAndMessageUnInitRefArg (C,C++, ObjC)
 """""""""""""""""""""""""""""""""""""""""""""""""""
 Check for logical errors for function calls and Objective-C
 message expressions (e.g., uninitialized arguments, null function pointers, and pointer to undefined variables).
 
 .. code-block:: c

 
 .. code-block:: cpp
 
  void deref_smart_ptr() {
    std::unique_ptr<int> P;
    *P; // warn: dereference of a default constructed smart unique_ptr
  }
 
+alpha.fuchsia
+^^^^^^^^^^^^^
+
+.. _alpha-fuchsia-lock:
+
+alpha.fuchsia.Lock
+""""""""""""""""""
+Similarly to :ref:`alpha.unix.PthreadLock <alpha-unix-PthreadLock>`, checks for
+the locking/unlocking of fuchsia mutexes.
+
+.. code-block:: cpp
+
+ spin_lock_t mtx1;
+
+ void bad1(void)
+ {
+   spin_lock(&mtx1);
+   spin_lock(&mtx1);  // warn: This lock has already been acquired
+ }
+
 alpha.llvm
 ^^^^^^^^^^
 
 .. _alpha-llvm-Conventions:
 
 alpha.llvm.Conventions
 """"""""""""""""""""""
 

clang/docs/analyzer/user-docs/CrossTranslationUnit.rst

.. code-block:: bash
   $ /your/path/to/llvm-project/clang/tools/scan-view/bin/scan-view /tmp/scan-build-2019-07-17-17-53-33-810365-7fqgWk
   Starting scan-view at: http://127.0.0.1:8181
     Use Ctrl-C to exit.
   [6336:6431:0717/175357.633914:ERROR:browser_process_sub_thread.cc(209)] Waited 5 ms for network service
   Opening in existing browser session.
   ^C
   $
 
+.. _ctu-on-demand:
+
 On-demand analysis
 __________________
 The analysis produces the necessary AST structure of external TUs during analysis. This requires the
 exact compiler invocations for each TU, which can be generated by hand, or by tools driving the analyzer.
 The compiler invocation is a shell command that could be used to compile the TU-s main source file.
 The mapping from absolute source file paths of a TU to lists of compilation command segments used to
 compile said TU are given in YAML format referred to as `invocation list`, and must be passed as an
 analyer-config argument.
 The index, which maps function USR names to source files containing them must also be generated by the
 `clang-extdef-mapping`. Entries in the index must *not* have an `.ast` suffix if the goal
 is to use On-demand analysis, as that extension signals that the entry is to be used as an PCH-dump.
 The mapping of external definitions implicitly uses a
 :doc:`compilation database <../../JSONCompilationDatabase>` to determine the compilation flags used.
 The analysis invocation must be provided with the directory which contains the mapping
 files, and the `invocation list` which is used to determine compiler flags.