merge main into amd-staging (llvm#3438)

Author: z1_cciauto

bolt/test/link_fdata.py

@@ -9,6 +9,7 @@
 
 import argparse
 import os
+import platform
 import shutil
 import subprocess
 import sys
@@ -19,7 +20,11 @@
 parser.add_argument("objfile", help="Object file to extract symbol values from")
 parser.add_argument("output")
 parser.add_argument("prefix", nargs="?", default="FDATA", help="Custom FDATA prefix")
-parser.add_argument("--nmtool", default="nm", help="Path to nm tool")
+parser.add_argument(
+    "--nmtool",
+    default="llvm-nm" if platform.system() == "Windows" else "nm",
+    help="Path to nm tool",
+)
 parser.add_argument("--no-lbr", action="store_true")
 parser.add_argument("--no-redefine", action="store_true")
 
@@ -86,7 +91,10 @@
             exit("ERROR: unexpected input:\n%s" % line)
 
 # Read nm output: <symbol value> <symbol type> <symbol name>
-is_llvm_nm = os.path.basename(os.path.realpath(shutil.which(args.nmtool))) == "llvm-nm"
+# Ignore .exe on Windows host.
+is_llvm_nm = os.path.basename(os.path.realpath(shutil.which(args.nmtool))).startswith(
+    "llvm-nm"
+)
 nm_output = subprocess.run(
     [
         args.nmtool,

clang-tools-extra/docs/clang-tidy/checks/bugprone/compare-pointer-to-member-virtual-function.rst

@@ -56,6 +56,7 @@ virtual functions, thereby improving the overall stability and maintainability
 of your code. In scenarios involving pointers to member virtual functions, it's
 only advisable to employ ``nullptr`` for comparisons.
 
+
 Limitations
 -----------
 

clang-tools-extra/docs/clang-tidy/checks/bugprone/copy-constructor-init.rst

@@ -35,7 +35,9 @@ outcomes. The check ensures that the copy constructor of a derived class
 properly calls the copy constructor of the base class, helping to prevent bugs
 and improve code quality.
 
-Limitations:
+
+Limitations
+-----------
 
 * It won't generate warnings for empty classes, as there are no class members
   (including base class sub-objects) to worry about.

clang-tools-extra/docs/clang-tidy/checks/bugprone/crtp-constructor-accessibility.rst

@@ -85,7 +85,9 @@ Example:
 
   CRTP<int> AlsoCompileTimeError;
 
-Limitations:
+
+Limitations
+-----------
 
 * The check is not supported below C++11
 

clang-tools-extra/docs/clang-tidy/checks/bugprone/nondeterministic-pointer-iteration-order.rst

@@ -35,7 +35,9 @@ This check only detects range-based for loops over unordered sets and maps. It
 also detects calls sorting-like algorithms on containers holding pointers.
 Other similar usages will not be found and are false negatives.
 
-Limitations:
+
+Limitations
+-----------
 
 * This check currently does not check if a nondeterministic iteration order is
   likely to be a mistake, and instead marks all such iterations as bugprone.

clang-tools-extra/docs/clang-tidy/checks/bugprone/redundant-branch-condition.rst

@@ -78,8 +78,9 @@ Every possible change is considered, thus if the condition variable is not
 a local variable of the function, it is a volatile or it has an alias (pointer
 or reference) then no warning is issued.
 
-Known limitations
-^^^^^^^^^^^^^^^^^
+
+Limitations
+-----------
 
 The ``else`` branch is not checked currently for negated condition variable:
 

clang-tools-extra/docs/clang-tidy/checks/bugprone/sizeof-expression.rst

@@ -266,8 +266,9 @@ This check corresponds to the CERT C Coding Standard rule
 `ARR39-C. Do not add or subtract a scaled integer to a pointer
 <http://wiki.sei.cmu.edu/confluence/display/c/ARR39-C.+Do+not+add+or+subtract+a+scaled+integer+to+a+pointer>`_.
 
+
 Limitations
-"""""""""""
+-----------
 
 Cases where the pointee type has a size of `1` byte (such as, and most
 importantly, ``char``) are excluded.

clang-tools-extra/docs/clang-tidy/checks/bugprone/standalone-empty.rst

@@ -30,7 +30,9 @@ A call to ``clear()`` would appropriately clear the contents of the range:
   ...
   v.clear();
 
-Limitations:
+
+Limitations
+-----------
 
 * Doesn't warn if ``empty()`` is defined and used with the ignore result in the
   class template definition (for example in the library implementation). These

clang-tools-extra/docs/clang-tidy/checks/misc/const-correctness.rst

@@ -52,8 +52,9 @@ Note that there is the check
 :doc:`cppcoreguidelines-avoid-non-const-global-variables <../cppcoreguidelines/avoid-non-const-global-variables>`
 to enforce ``const`` correctness on all globals.
 
-Known Limitations
------------------
+
+Limitations
+-----------
 
 The check does not run on `C` code.
 

clang-tools-extra/docs/clang-tidy/checks/misc/no-recursion.rst

@@ -14,7 +14,9 @@ References:
 * JPL Institutional Coding Standard for the C Programming Language (JPL DOCID D-60411) rule `2.4 Do not use direct or indirect recursion`.
 * OpenCL Specification, Version 1.2 rule `6.9 Restrictions: i. Recursion is not supported. <https://www.khronos.org/registry/OpenCL/specs/opencl-1.2.pdf>`_.
 
-Limitations:
+
+Limitations
+-----------
 
 * The check does not handle calls done through function pointers
 * The check does not handle C++ destructors