Changes

[lldb] Only run the shell test for the Xcode standalone build

Allow arbitrary capability name in Thread Safety Analysis
Restricting the names of capabilities to only "role" or "mutex" makes 
for awkward diagnostic text, such as with: 
https://chromium-review.googlesource.com/c/chromium/src/+/1948098/19/base/sequence_checker_unittest.nc#33

Removing an accidentally duplicated line of test code to fix bots.

Revert "[Clang] Un-break scan-build after integrated-cc1 change"
This reverts commit a6883017ea9af529e89d7f89af2477378b6eafca.

Revert "List implicit operator== after implicit destructors in a
vtable."
This reverts commit add2b7e44ada46f30715b5c48823a9e9e317e0c3.
Failed "Clang::virtual-compare.cpp" test on the arm builders. See 
http://lab.llvm.org:8011/builders/llvm-clang-win-x-armv7l/builds/3169 
for details.

[lldb/CMake] Add check-lldb-shell and check-lldb-api targets for Xcode
The Xcode generator does not provide the auto-generated targets where 
you can append a folder name to check-lldb. Instead add two custom lit 
targets to run just the shell and api tests.

AMDGPU/GlobalISel: Legalize G_PTR_ADD for arbitrary pointers
Pointers of unrecognized address spaces shoudl be treated as global-like
pointers. Even if loads and stores of them aren't handled, dumb
operations that just operate on the bits should work.

[lldb/DataFormatters] Fix the `$$deference$$` synthetic child
Summary: The ValueObject code checks for a special `$$dereference$$`
synthetic child to allow formatter providers to implement a natural 
dereferencing behavior in `frame variable` for objects like smart 
pointers.
This support was broken when used directly throught the Python API and 
not trhough `frame variable`. The reason is that SBFrame.FindVariable()
will return by default the synthetic variable if it exists, while `frame
variable` will not do this eagerly. The code in
`ValueObject::Dereference()` accounted for the latter but not for the
former. The fix is trivial. The test change includes additional
covergage for the already-working bahevior as it wasn't covered by the
testsuite before.
This commit also adds a short piece of documentatione explaining that it
is possible (even advisable) to provide this synthetic child outstide of
the range of the normal children.
Reviewers: jingham
Subscribers: lldb-commits
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D73053

[APInt] Fix tests that had wrong assumption about sdivs with negative
quotient.
Reviewers: sanjoy
Subscribers: bixia, dexonsmith, sanjoy.google, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D70156

AMDGPU/GlobalISel: Merge G_PTR_ADD/G_PTR_MASK rules

[PATCH] Reland [Clang] Un-break scan-build after integrated-cc1 change
The issue was reported by @xazax.hun here:
https://reviews.llvm.org/D69825#1827826
"This patch (D69825) breaks scan-build-py which parses the output of
"-###" to get -cc1 command. There might be other tools with the same
problems. Could we either remove (in-process) from CC1Command::Print or
add a line break?
Having the last line as a valid invocation is valuable and there might
be tools relying on that."
Differential Revision: https://reviews.llvm.org/D72982

[SLP] Add a test showing miscompilation in AltOpcode support
Reviewers: Vasilis, RKSimon, ABataev
Reviewed By: RKSimon, ABataev
Subscribers: ABataev, inglorion, dexonsmith, llvm-commits, vdmitrie
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D72739

[Matrix] Hide and describe matrix-propagate-shape option.

[IR] Value::getPointerAlignment(): handle pointer constants
Summary: New `@test13` in `Attributor/align.ll` is the main motivation -
`null` pointer really does not limit our alignment knowledge, in fact it
is fully aligned since it has no bits set.
Here we don't special-case `null` pointer because it is somewhat
controversial to add one more place where we enforce that `null` pointer
is zero, but instead we do the more general thing of trying to perform
constant-fold of pointer constant to an integer, and perform alignment
inferrment on that.
Reviewers: jdoerfert, gchatelet, courbet, sstefan1
Reviewed By: jdoerfert
Subscribers: hiraditya, arphaman, jfb, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D73131

AMDGPU/GlobalISel: Merge trivial legalize rules
Also move constant-like rules together

[AArch64] Add custom store lowering for 256 bit non-temporal stores.
Currently we fail to lower non-termporal stores for 256+ bit vectors to
STNPQ, because type legalization will split them up to 128 bit stores 
and because there are no single non-temporal stores, creating STPNQ in
the Load/Store optimizer would be quite tricky.
This patch adds custom lowering for 256 bit non-temporal vector stores 
to improve the generated code.
Reviewers: dmgreen, samparker, t.p.northover, ab
Reviewed By: dmgreen
Differential Revision: https://reviews.llvm.org/D72919

Fix an over-suspend bug with LaunchInNewTerminalWithAppleScript sessions
When launching an inferior in a new terminal window via AppleScript and
the darwin-debug helper program, we could often end up with the inferior
process having a too-high suspend count, and it would never resume
execution.
lldb tries to wait until darwin-debug has finished its work and has 
launched the inferior (WaitForProcessToSIGSTOP) but this wasn't working
correctly - and cannot be made to work.
This patch removes WaitForProcessToSIGSTOP, adds a special tiny segment
to the darwin-debug executable so it can be identified as that binary
(ExecExtraSuspend), and adds code to debugserver to detect this segment.
 When debugserver sees this segment, it notes that the next exec will be
done with a launch-suspended flag.  When the next exec happens,
debugserver forces an extra task_resume when we resume the inferior.
An alternative approach would be if lldb could detect when the inferior
has been launched by darwin-debug unambiguously; monitoring when the
unix socket between darwin-debug and lldb was closed would have been a
reasonable way to do this too.
<rdar://problem/29760580>
Differential Revision: https://reviews.llvm.org/D72963

[lldb/Plugin] Rename AddressSanitizerRuntime for consistency with plugin
(NFC)
Renames AddressSanitizerRuntime to InstrumentationRuntimeASan to be 
consistent with the directory structure and plugin name.

[lldb/Plugin] Rename TSanRuntime for consistency with plugin (NFC)
Renames TSanRuntime to InstrumentationRuntimeTSan to be consistent with
the directory structure and plugin name.

[lldb/Plugin] Rename UBSanRuntime for consistency with plugin (NFC)
Renames UBSanRuntime to InstrumentationRuntimeUBSan to be consistent 
with the directory structure and plugin name.

[lldb/Plugin] Rename MainThreadCheckerRuntime for consistency with
plugin (NFC)
Renames MainThreadCheckerRuntime to 
InstrumentationRuntimeMainThreadChecker to be consistent with the 
directory structure and plugin name.

[lldb/Plugin] Move DisassemblerLLVMC for consistency with plugin (NFC)
Rename the DisassemblerLLVMC directory from llvm to LLVMC to match the 
plugin name.

[SLP] Don't allow Div/Rem as alternate opcodes
Summary: We don't have control/verify what will be the RHS of the
division, so it might happen to be zero, causing UB.
Reviewers: Vasilis, RKSimon, ABataev
Reviewed By: ABataev
Subscribers: vporpo, ABataev, hiraditya, llvm-commits, vdmitrie
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D72740

Fix typos

List implicit operator== after implicit destructors in a vtable.
Summary: We previously listed first declared members, then implicit
operator=, then implicit operator==, then implicit destructors. Per
discussion on https://github.com/itanium-cxx-abi/cxx-abi/issues/88, put
the implicit equality comparison operators at the very end, after all
special member functions.
This reinstates add2b7e44ada46f30715b5c48823a9e9e317e0c3, reverted in 
commit 89e43f04ba87a0da6e94863db149669c7536486b, with a fix for 32-bit 
targets.
Reviewers: rjmccall
Subscribers: cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D72897

[Concepts] Placeholder constraints and abbreviated templates
This patch implements P1141R2 "Yet another approach for constrained
declarations".
General strategy for this patch was:
- Expand AutoType to include optional type-constraint, reflecting the
wording and easing the integration of constraints.
- Replace autos in parameter type specifiers with invented parameters in
GetTypeSpecTypeForDeclarator, using the same logic
 previously used for generic lambdas, now unified with abbreviated
templates, by:
 - Tracking the template parameter lists in the Declarator object
 - Tracking the template parameter depth before parsing function
declarators (at which point we can match template
   parameters against scope specifiers to know if we have an explicit
template parameter list to append invented parameters
   to or not).
- When encountering an AutoType in a parameter context we check a stack
of InventedTemplateParameterInfo structures that
 contain the info required to create and accumulate invented template
parameters (fields that were already present in
 LambdaScopeInfo, which now inherits from this class and is looked up
when an auto is encountered in a lambda context).
Differential Revision: https://reviews.llvm.org/D65042

[lldb] Only run the shell test for the Xcode standalone build