Changes

Revert "[WebAssembly] Track frame registers through VReg and local
allocation"
This reverts commit 3a05c3969c18b5520e360b78fc63cda39a6be98f. It breaks
under expensive-checks and on Windows

lldb: xfail TestCrossDSOTailCalls.py and TestCrossObjectTailCalls.py on
arm/aarch64
This effectively reverts commit 
8d2f252bb8e4d199be8498c4ee2245117ef08fd2, which went a bit too far and 
disabled these on all non-Darwin systems.

[libcxx] Temporarily switch back to pthread backend for Fuchsia
We switched to C11 thread API on Fuchsia in ab9aefe, but further testing
showed that Fuchsia's C11 mutex implementation needs a few improvements
for this to be usable, so we temporarily switch back to the pthread
implementation until those issues are addressed.
Differential Revision: https://reviews.llvm.org/D72862

[lld][WebAssembly] Use a more meaningful name for stub functions
When we generate these stub functions on signature mismatches give them
a more meaningful name so that when people see this in stack traces is
gives a clue as the what is going on.
See: https://github.com/emscripten-core/emscripten/issues/10226
Differential Revision: https://reviews.llvm.org/D72881

[mlir] NFC: Fix trivial typos
Summary: Fix trivial typos
Differential Revision: https://reviews.llvm.org/D72672

[mlir] support translation of multidimensional vectors to LLVM IR
Summary: MLIR unlike LLVM IR supports multidimensional vector types.
Such types are lowered to nested LLVM IR arrays wrapping an LLVM IR
vector for the innermost dimension of the MLIR vector. MLIR supports
constants of such types using ElementsAttr for values. Introduce support
for converting ElementsAttr into LLVM IR Constant Aggregates
recursively. This enables translation of multidimensional vector
constants from MLIR to LLVM IR.
Differential Revision: https://reviews.llvm.org/D72846

[clangd][test] Disable a particular testcase in
FindExplicitReferencesTest when LLVM_ENABLE_EXPENSIVE_CHECKS
The test is failing on our CI bots. Seems like the order of results for
one target is undefined.
(post-commit review) Differential Revision:
https://reviews.llvm.org/D72883

AMDGPU: Update clang test

[OPENMP]Do not emit RTTI descriptor for NVPTX devices.
Need to disable emission of RTTI descriptors for NVPTX devices to be 
able to use dynamic classes without unresolved symbols at link stage.

[AArch64][GlobalISel] Change G_FCONSTANTs feeding into stores into
G_CONSTANTS
Given the following situation:
x = G_FCONSTANT (something that can't be materialized) G_STORE x,
some_addr
We know that x must be materialized as at least a single mov. However,
at the time of selection, the G_STORE will have been regbankselected to
a FPR store.
So, as a result, you'll get an unnecessary fmov into the G_STORE.
Storing a constant value in a GPR and a constant value in a FPR are the
same. So, whenever you see a G_FCONSTANT that feeds into only G_STORES,
so might as well make it a G_CONSTANT.
This adds a target-specific combine which changes G_FCONSTANTs feeding
into G_STOREs into G_CONSTANTs.
Differential Revision: https://reviews.llvm.org/D72814

[NFC] Fold isHugeExpression into hasHugeExpression and update callers
accordingly.

PointerLikeTypeTraits: Standardize NumLowBitsAvailable on static
constexpr rather than anonymous enum
This is (more?) usable by GDB pretty printers and seems nicer to write.
There's one tricky caveat that in C++14 (LLVM's codebase today) the 
static constexpr member declaration is not a definition - so odr use of 
this constant requires an out of line definition, which won't be 
provided (that'd make all these trait classes more annoyidng/expensive 
to maintain). But the use of this constant in the library implementation 
is/should always be in a non-odr context - only two unit tests needed to 
be touched to cope with this/avoid odr using these constants.
Based on/expanded from D72590 by Christian Sigg.

[mlir] Add missing dependency on LinalgUtils
Differential Revision: https://reviews.llvm.org/D72821

Make LLVM_APPEND_VC_REV=OFF affect clang, lld, and lldb as well.
When LLVM_APPEND_VC_REV=OFF is set, the current git hash is no longer
embedded into binaries (mostly for --version output). Without it, most
binaries need to relink after every single commit, even if they didn't
change otherwise (due to, say, a documentation-only commit).
LLVM_APPEND_VC_REV is ON by default, so this doesn't change the default
behavior of anything.
With this, all clients of GenerateVersionFromVCS.cmake honor 
LLVM_APPEND_VC_REV.
Differential Revision: https://reviews.llvm.org/D72855

[gn build] replace llvm_allow_tardy_revision with llvm_append_vc_rev
Previously, the gn build would create VCSRevision.h / VCSVersion.h files
with some LLD_REVISION / LLVM_REVISION / CLANG_REVISION but by default
wouldn't add a dependency on .git/logs/HEAD so that the step doesn't
rerun after every branch switch or every pull.
That's bad for deterministic builds, and having --version print some
arbitrarily old revision isn't great either.
Instead, move to the model that the cmake build (now) uses fairly 
consistently: If llvm_append_vc_rev is set, include the revision, else
don't.
Since the GN build is focused on developers, set llvm_append_vc_rev to
false instead of true by default (different from the cmake build), so
that things don't rebuild after every branch switch and every pull.
While here, also remove some pre-monorepo code.
Differential Revision: https://reviews.llvm.org/D72859

Move static function to inline function - this fixes a conceivable ODR
violation and a clang-tidy warning about an unused function in a number
of translation units.

Add back other PowerPC link components.
Add the link components back to unblock bots for the moment. In the 
meantime, I'm investigating the BUILD_SHARED_LIBS=ON build to find out
the minimal list of components needed.

[FastISel] Lower `llvm.dbg.value(undef, ...` correctly.
Summary: Instead of just dropping them.
<rdar://problem/58657146>
Reviewers: aprantl, vsk, ab, paquette, echristo
Subscribers: hiraditya, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D72877

[xray] add --no-demangle cli opt for llvm-xray extract to output mangled
names
This adds an additional cli flag for the llvm-xray extract tool.  This 
is useful if you're more interested in consuming the mangled symbol 
name, instead of the default now which is demangled.
Differential Revision: https://reviews.llvm.org/D72804

[lldb/Debugger] Rename ExecuteIOHandlers to RunIOHandlers (NFC)
This improves consistency among the related methods.

Add testing for DW_OP_piece and fix a bug with small Scalar values.
By switching to Scalars that are backed by explicitly-sized APInts we 
can avoid a bug that increases the buffer reserved for a small piece to
the next-largest host integer type.
This manifests as "DW_OP_piece for offset foo but top of stack is of
size bar".
Differential Revision: https://reviews.llvm.org/D72879

Fix a buffer-size bug when the first DW_OP_piece is undefined
and document the shortcomings of LLDB's partially defined DW_OP_piece 
handling.
This would manifest as "DW_OP_piece for offset foo but top of stack is 
of size bar".
rdar://problem/46262998
Differential Revision: https://reviews.llvm.org/D72880

[modules] Do not cache invalid state for modules that we attempted to
load.
Partially reverts 0a2be46cfdb698fefcc860a56b47dde0884d5335 as it turned 
out to cause redundant module rebuilds in multi-process incremental
builds. When a module was getting out of date, all compilation processes
started at the same time were marking it as `ToBuild`. So each process
was building the same module instead of checking if it was built by
someone else and using that result. In addition to the work duplication,
contention on the same .pcm file wasn't making builds faster.
Note that for a single-process build this change would cause redundant
module reads and validations. But reading a module is faster than
building it and multi-process builds are more common than
single-process. So I'm willing to make such a trade-off.
rdar://problem/54395127
Reviewed By: dexonsmith
Differential Revision: https://reviews.llvm.org/D72860

Add back more link components.
Add all previous link components back to unblock bots for the moment. In
the meantime, I'm investigating the BUILD_SHARED_LIBS=ON build to find
out the minimal list of components needed.

Revert "[RISCV] Support ABI checking with per function target-features"
This reverts commit 7bc58a779aaa1de56fad8b1bc8e46932d2f2f1e4. It breaks
EXPENSIVE_CHECKS on Windows

Add extra test file forgotten in 45d7080.

[NFC][PowerPC] Remove unnecessary link components.
Remove unused link components for PowerPC target unittest according to
post commit comments. This is a redo for a previous commit
"fc4e43ad618b" that removed a few components that are necessary when
libraries are to be built shared (i.e., BUILD_SHARED_LIBS=ON).

[mlir][spirv] Add implied capabilities and availability for capabilities
Certain SPIR-V capabilities are only available in certain SPIR-V
versions or extensions. Also a SPIR-V capability may implicitly declares
other capabilities.
This commit updates gen_spirv_dialect.py to support generating such 
information into SPIRVBase.td. It requires us to topologically sort all
capabilities because now a capability can refer to another one.
This commits also registers a few extensions because their symbols are 
used by capability availability.
Note that this commit hasn't updated SPIRVConversionTarget to take into
consideration such relationship yet. That will be done in a following-up
commit.
Differential Revision: https://reviews.llvm.org/D72760

[mlir][spirv] Use symbolize functions in enum attribute predicates
By default, for an enum attribute, we will generate a list of equality 
comparisons for all supported cases inside it's predicate. This list can
be fairly large for certain SPIR-V enum attributes. Instead, we already
have such a list generated by EnumsGen in the symbolize functions.
Leverage that to simplify the generated C++ code.
Differential Revision: https://reviews.llvm.org/D72763

[mlir][spirv] Fix SPV_MM_Vulkan extension reqirements
SPV_MM_Vulkan can be enabled by the SPV_KHR_vulkan_memory_model
extension.
Differential Revision: https://reviews.llvm.org/D72764

Avoid creating an immutable map in the Automaton class.
Summary: In the DFAPacketizer we copy the Transitions array into a map
in order to later access the transitions based on a "Current
State/Action" pair as a key. This map lives in the Automaton object used
by the DFAPacketizer. It is never changed during the life of the object
after having been created during the creation of the Automaton itself.
This map creation can make the creation of a DFAPacketizer quite
expensive if the target contains a considerable amount of transition
states.
Considering that TableGen already generates a sorted list of transitions
by State/Action pairs we could just use that directly in our Automaton 
and search entries with std::lower_bound instead of copying it in a map
and paying the execution time and memory cost.
Reviewers: jmolloy, ThomasRaoux
Subscribers: llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D72682

AMDGPU: Add register classes to MUBUF load patterns

Don't dump IR output from this test to stdout.

[lldb] add to gdb to lldb doc
Summary: * enabling and disabling a breakpoint were missing.
Reviewers: JDevlieghere
Reviewed By: JDevlieghere
Subscribers: merge_guards_bot, jingham, dexonsmith, ributzka,
lldb-commits
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D72898

[lldb/CMake] Set LLVM_HOST_TRIPLE from TARGET_TRIPLE in standalone
builds.
LLVMConfig doesn't export LLVM_HOST_TRIPLE, but it sets the 
TARGET_TRIPLE based on this variable. So use that again for the compiler 
invocations in the shell tests.

[docs][ORC] Update the "utilities" section, tidy intro and fix typo.
This patch updates the formatting and language of the Features section
of the ORCv2 design document. It also fixes a TBD by adding discussion
of the absoluteSymbols, symbolAliases, and reexports utilities.
Typos found during editing were also fixed.

[lldb/CMake] Remove duplicate entry