[NFC] Trim trailing whitespace in *.rst

clang-tools-extra/docs/clang-tidy/checks/bugprone-signal-handler.rst

@@ -34,4 +34,3 @@ and has an alias name ``cert-sig30-c``.
   Functions registered as exit handlers are not checked.
 
   Default is ``POSIX``.
-

clang-tools-extra/docs/clang-tidy/checks/cppcoreguidelines-no-malloc.rst

@@ -43,4 +43,3 @@ Options
 
    Semicolon-separated list of fully qualified names of memory allocation functions.
    Defaults to ``::realloc``.
-

clang-tools-extra/docs/clang-tidy/checks/hicpp-exception-baseclass.rst

@@ -27,4 +27,3 @@ of the High Integrity C++ Coding Standard.
     throw std::runtime_error();
     throw std::exception();
   }
-  

clang-tools-extra/docs/clang-tidy/checks/list.rst

@@ -451,4 +451,3 @@ Clang-Tidy Checks
    `hicpp-vararg <hicpp-vararg.html>`_, `cppcoreguidelines-pro-type-vararg <cppcoreguidelines-pro-type-vararg.html>`_,
    `llvm-else-after-return <llvm-else-after-return.html>`_, `readability-else-after-return <readability-else-after-return.html>`_, "Yes"
    `llvm-qualified-auto <llvm-qualified-auto.html>`_, `readability-qualified-auto <readability-qualified-auto.html>`_, "Yes"
-   

clang-tools-extra/docs/clang-tidy/checks/performance-faster-string-find.rst

@@ -27,4 +27,3 @@ Options
    The check will only consider member functions named ``find``, ``rfind``,
    ``find_first_of``, ``find_first_not_of``, ``find_last_of``, or
    ``find_last_not_of`` within these classes.
-

clang-tools-extra/docs/pp-trace.rst

@@ -822,4 +822,3 @@ To build from source:
 .. _Getting Started with the LLVM System: https://llvm.org/docs/GettingStarted.html
 .. _Building LLVM with CMake: https://llvm.org/docs/CMake.html
 .. _Clang Tools Documentation: https://clang.llvm.org/docs/ClangTools.html
-

clang/docs/InternalsManual.rst

@@ -3265,4 +3265,3 @@ are similar.
      proper visitation for your expression, enabling various IDE features such
      as syntax highlighting, cross-referencing, and so on.  The
      ``c-index-test`` helper program can be used to test these features.
-

clang/docs/RAVFrontendAction.rst

@@ -224,4 +224,3 @@ declarations of a class n::m::C it found:
 
       $ ./bin/find-class-decls "namespace n { namespace m { class C {}; } }"
       Found declaration at 1:29
-

clang/docs/ThreadSafetyAnalysis.rst

@@ -1041,4 +1041,3 @@ implementation.
   #endif  // USE_LOCK_STYLE_THREAD_SAFETY_ATTRIBUTES
 
   #endif  // THREAD_SAFETY_ANALYSIS_MUTEX_H
-

clang/docs/analyzer/developer-docs.rst

@@ -11,4 +11,3 @@ Contents:
    developer-docs/InitializerLists
    developer-docs/nullability
    developer-docs/RegionStore
-   

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

@@ -374,4 +374,3 @@ We actively develop CTU with CodeChecker as the driver for feature, `scan-build-
 `scan-build-py` has various errors and issues, expect it to work only with the very basic projects only.
 
 Currently On-demand analysis is not supported with `scan-build-py`.
-

lld/MachO/ld64-vs-lld.rst

@@ -13,4 +13,3 @@ There are differences in how LLD and LD64 handle ObjC symbols loaded from archiv
    * Duplicate ObjC symbols from different archives will raise a "duplicate symbol" error.
 - LLD:
    * Duplicate symbols, regardless of which archives they are from, will raise errors.
-

llvm/docs/BigEndianNEON.rst

@@ -202,4 +202,3 @@ For the previous example, this would be::
 It turns out that these ``REV`` pairs can, in almost all cases, be squashed together into a single ``REV``. For the example above, a ``REV128 4s`` + ``REV128 2d`` is actually a ``REV64 4s``, as shown in the figure on the right.
 
 .. [1] One lane vectors may seem useless as a concept but they serve to distinguish between values held in general purpose registers and values held in NEON/VFP registers. For example, an ``i64`` would live in an ``x`` register, but ``<1 x i64>`` would live in a ``d`` register.
-

llvm/docs/HowToReleaseLLVM.rst

@@ -375,4 +375,3 @@ Announce the Release
 
 Send an email to the list announcing the release, pointing people to all the
 relevant documentation, download pages and bugs fixed.
-

llvm/docs/MCJITDesignAndImplementation.rst

@@ -177,4 +177,3 @@ Finally, MCJIT calls the memory manager's finalizeMemory method.  In this
 method, the memory manager will invalidate the target code cache, if
 necessary, and apply final permissions to the memory pages it has
 allocated for code and data memory.
-

llvm/docs/NVPTXUsage.rst

@@ -969,4 +969,3 @@ This gives us the following PTX (excerpt):
     st.global.f32   [%rl1], %f110;
     ret;
   }
-

llvm/docs/ProgrammersManual.rst

@@ -4095,5 +4095,3 @@ The ``Argument`` class
 This subclass of Value defines the interface for incoming formal arguments to a
 function.  A Function maintains a list of its formal arguments.  An argument has
 a pointer to the parent Function.
-
-

llvm/docs/Statepoints.rst

@@ -819,4 +819,3 @@ with most LLVM features, design discussions take place on `llvm-dev
 <http://lists.llvm.org/mailman/listinfo/llvm-dev>`_, and patches
 should be sent to `llvm-commits
 <http://lists.llvm.org/mailman/listinfo/llvm-commits>`_ for review.
-

llvm/docs/TableGen/BackEnds.rst

@@ -967,4 +967,3 @@ This use of ``SearchIndex`` generates the following additional C++ code.
       return nullptr;
     return &CTable[Idx->_index];
   }
-

llvm/docs/WritingAnLLVMBackend.rst

@@ -1976,4 +1976,3 @@ The callback function initially saves and later restores the callee register
 values, incoming arguments, and frame and return address.  The callback
 function needs low-level access to the registers or stack, so it is typically
 implemented with assembler.
-

llvm/docs/WritingAnLLVMPass.rst

@@ -1440,4 +1440,3 @@ multithreaded constructs, requiring only the LLVM core to have locking in a few
 places (for global resources).  Although this is a simple extension, we simply
 haven't had time (or multiprocessor machines, thus a reason) to implement this.
 Despite that, we have kept the LLVM passes SMP ready, and you should too.
-

llvm/docs/XRayExample.rst

@@ -345,5 +345,3 @@ making things better.
     XRay traces.
   - Collecting function call stacks and how often they're encountered in the
     XRay trace.
-
-

llvm/docs/YamlIO.rst

@@ -1031,5 +1031,3 @@ object.  For example:
      // Check for error
      if ( yin.error() )
        return;
-
-

openmp/docs/optimizations/OpenMPOpt.rst

@@ -106,4 +106,3 @@ Resources
 - 2021 OpenMP Webinar: "A Compiler's View of OpenMP" https://youtu.be/eIMpgez61r4
 - 2020 LLVM Developers’ Meeting: "(OpenMP) Parallelism-Aware Optimizations" https://youtu.be/gtxWkeLCxmU
 - 2019 EuroLLVM Developers’ Meeting: "Compiler Optimizations for (OpenMP) Target Offloading to GPUs" https://youtu.be/3AbS82C3X30
-