Changes

[Concepts] Fix bug when referencing function parameters in instantiated
function template requires clause
Fixes bug #44613 - incorrect instantiated parameters were being added
when checking instantiated function constraints

[gn build] reformat all build files again
Run `git ls-files '*.gn' '*.gni' | xargs llvm/utils/gn/gn.py format` 
after recent fixes to formatting of comments after single-element lists.

Add LLVM_VALUE_FUNCTION to Optional::map(); NFC
This is for future-proofing when compiling with MSVC once we drop
support for 2017.

AMDGPU/R600: Emit rodata in text segment
R600 relies on this behaviour. Fixes:
6e18266aa4dd78953557b8614cb9ff260bad7c65 ('Partially revert D61491
"AMDGPU: Be explicit about whether the high-word in SI_PC_ADD_REL_OFFSET
is 0"') Fixes ~100 piglit regressions since 6e18266
Differential Revision: https://reviews.llvm.org/D72991

[mlir] Add baseAttr to TypedArrayAttrBase.
Element type is useful in code generators but it is lost after
construction.
Differential Revision: https://reviews.llvm.org/D72888

[LoopDeletion] Teach LoopDeletion to preserve MemorySSA if available.
If MemorySSA analysis is analysis, LoopDeletion now preserves it.

Add a bit of documentation on attribute spellings that were missing.

Extend misc-misplaced-const to detect using declarations as well as
typedef

[SVE] Pass Scalable argument to VectorType::get in Bitcode Reader
Pass the Scalability test to VectorType::get in order to be able to 
deserialize bitcode that contains scalable vector operations
Differential Revision: https://reviews.llvm.org/D73144

[x86] fold vperm2x128 to concat of 128-bit high half vectors
vperm (ins ?, X, C), (ins ?, Y, C), 0x31 --> concat X, Y
This is another shuffle problem seen with PR42024: 
https://bugs.llvm.org/show_bug.cgi?id=42024
We have this small crack in legalization/lowering/combining/demanded 
that allows forming a vperm2f128 of high halves with AVX1 when we could
do better by peeking through the insert_subvector nodes. AFAICT, it
requires IR as shown in the diffs - much larger than legal vectors - to
avoid all of the usual folds.
Another option would prevent forming the 256-bit vperm in lowering.
Differential Revision: https://reviews.llvm.org/D73197

[llvm-cov] Add support for -skip-functions to lcov
Summary: This flag was added for the json format to exclude functions
from the output. This mirrors that behavior in lcov (where it was
previously accepted but ignored). This makes the output file smaller
which can be beneficial depending on how you consume it, especially if
you don't use this data anyways.
Patch by Keith Smiley (@keith).
Reviewers: kastiglione, Dor1s, vsk, allevato
Reviewed By: Dor1s, allevato
Subscribers: llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D73160

[libFuzzer] Add INFO output when LLVMFuzzerCustomMutator is found.
Summary: there is an ongoing work on interchangeable custom mutators
(https://github.com/google/clusterfuzz/pull/1333/files#r367706283) and
having some sort of signalling from libFuzzer that it has loaded a
custom mutator would be helpful.
The initial idea was to make the mutator to print something, but given 
the anticipated variety of different mutators, it does not seem possible 
to make all of them print the same message to signal their execution.
Reviewers: kcc, metzman
Reviewed By: metzman
Subscribers: #sanitizers, llvm-commits
Tags: #sanitizers, #llvm
Differential Revision: https://reviews.llvm.org/D73136

R600: Fix failing testcase

Convert AssertTrue( A == B) to AssertEqual(A, B) in TestObjCStepping.py.

[lldb/Util] Fix lldb-repro now it doesn't take a path to lldb
The indices into the arguments array were off because we no longer pass 
the path to lldb as the first argument.

[lldb/Test] Use lit's capabilities to skip lldb-repro tests.
This allows us to skip the reproducer tests themselves as a whole as 
well as individual tests with the UNSUPPORTED keyword.

[lldb/Reproducer] Correctly instrument enum values
Enum values can be serialized trivially and should not go through the 
object registry.

[ODRHash] Factor out functionality for CXXRecord ODR diagnostics (NFCI)
There's going to be a lot of common code between RecordDecl and 
CXXRecordDecl, factor out some of the logic in preparation for adding
the RecordDecl side.

[PatternMatch] Add m_APInt/m_APFloat matchers accepting undef
The current m_APInt() and m_APFloat() matchers do not accept splats that
include undefs (unlike m_Zero() and other matchers for specific values).
We can't simply change the default behavior, as there are existing
transforms that would not be safe with undefs.
For this reason, I'm introducing new m_APIntAllowUndef() and 
m_APFloatAllowUndef() matchers, that allow splats with undefs. 
Additionally, m_APIntForbidUndef() and m_APFloatForbidUndef() are added.
These have the same behavior as the existing m_APInt() and m_APFloat(),
but serve as an explicit indication that undefs were considered and
found unsound for this transform. This helps distinguish them from
existing uses of m_APInt() where we do not know whether undefs can or
cannot be allowed without additional review.
Differential Revision: https://reviews.llvm.org/D72975

Clang] Fix expansion of response files in -Wp after integrated-cc1
change
After rGb4a99a061f517e60985667e39519f60186cbb469, passing a response
file such as -Wp,@a.rsp wasn't working anymore because .rsp expansion
happens inside clang's main() function.
This patch adds response file expansion in the -cc1 tool.
Differential Revision: https://reviews.llvm.org/D73120

[PowerPC] Collect some CallLowering arguments into a struct. [NFC]
Collect the calling convention and a number of boolean arguments into a 
structure to slightly reduces the number of arguments passed around
between LowerCall_<Subtarget>, FinishCall and a few of the helpers. Also 
calulates if a call is indirect once using the exisitng helper and
caches the result replacing several instances where we duplicated the
logic determining if a call is indirect.

[PatternMatch] Make m_c_ICmp swap the predicate (PR42801)
This addresses https://bugs.llvm.org/show_bug.cgi?id=42801. The
m_c_ICmp() matcher is changed to provide the swapped predicate if the
operands are swapped.
Existing uses of m_c_ICmp() fall in one of two categories: Working on
equality predicates only, where swapping is irrelevant. Or performing a
manual swap, in which case this patch removes it.
The only exception is the foldICmpWithLowBitMaskedVal() fold, which does
not swap the predicate, and instead reasons about whether a swap
occurred or not for each predicate. Getting the swapped predicate allows
us to merge the logic for pairs of predicates, instead of duplicating
it.
Differential Revision: https://reviews.llvm.org/D72976

[TestStdModuleSysroot] Only run locally.

[mlir][Linalg] Add tensor support to Linalg EDSC Builders
Summary: This diff extends the Linalg EDSC builders so we can easily
create mixed tensor/buffer linalg.generic ops. This is expected to be
useful for HLO -> Linalg lowering.
The StructuredIndexed struct is made to derive from ValueHandle and can 
now capture a type + indexing expressions. This is used to represent
return tensors.
Pointwise unary and binary builders are extended to allow both output
buffers and return tensors. This has implications on the number of
region arguments.
Reviewers: ftynse, hanchung, asaadaldien
Subscribers: mehdi_amini, rriddle, jpienaar, burmako, shauheen,
antiagainst, arpith-jacob, mgester, lucyrfox, aartbik, liufengdb,
llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D73149

[X86] Cast to __v4hi instead of __m64 in the implementation of
_mm_extract_pi16 and _mm_insert_pi16.
__m64 is a vector of 1 long long. But the builtins these intrinsics are
calling expect a vector of 4 shorts.
Fixes PR44589

[InstCombine] Add test for PR44529; NFC

[InstCombine] Combine neg of shl of sub (PR44529)
Fixes https://bugs.llvm.org/show_bug.cgi?id=44529. We already have a
combine to sink a negation through a left-shift, but it currently only
works if the shift operand is negatable without creating any 
instructions. This patch introduces freelyNegateValue() as a more 
powerful extension of dyn_castNegVal(), which allows negating a value as
long as this doesn't end up increasing instruction count. Specifically,
this patch adds support for negating A-B to B-A.
This mechanism could in the future be extended to handle general 
negation chains that a) start at a proper 0-X negation and b) only 
require one operand to be freely negatable. This would end up as a 
weaker form of D68408 aimed at the most obviously profitable subset that
eliminates a negation entirely.
Differential Revision: https://reviews.llvm.org/D72978

[www] Update cxx_status page to list changes on the Clang 10 branch as
"Clang 10" not "SVN".

[lldb/Utility] Don't forward directories to the file collector
The VFS mapping writer assumes that all the paths it gets are files. 
When passed a directory, it ends up as a file in the VFS mapping twice, 
once as a file and once as a directory.
  {
   'type': 'file',
   'name': "Output",
   'external-contents': "/root/path/to/Output"
 },
 {
   'type': 'directory',
   'name': "Output",
   'contents': [ ... ]
 }

[lldb/Test] Skip script interpreter tests reading from stdin for
lldb-repro
The reproducers currently only shadow the command interpreter. It would 
be possible to make it work for the Lua interpreter which uses the 
IOHandlerEditline under the hood, but the Python one runs a REPL in 
Python itself so there's no (straightforward) way to shadow that.
Given that we already capture any API calls, this isn't super high on my 
list of priorities.

[LoopIdiomRecognize] Reduce variable scope. [NFCI]

[IndVarSimplify] Cleanup spaces and reduce variable scope [NFCI]
Minor clean-ups + clang-format.

Embed a zero-length /dev/null in darwin-debug for the special section.
Fred suggested that instead of embedded CMakeLists.txt in the binary as 
the contents of a special section, see if /dev/null would work.  It 
does.

[nfc][libomptarget] Remove SHARED annotation from local variables
Summary:
[nfc][libomptarget] Remove SHARED annotation from local variables
A few local variables in reduction.cu were marked SHARED. This patch
leaves all per-kernel global state localised in omp_data.cu.
Reviewers: ABataev, jdoerfert, grokos
Reviewed By: jdoerfert
Subscribers: openmp-commits
Tags: #openmp
Differential Revision: https://reviews.llvm.org/D73239

[cmake] Fix clang builds with BUILD_SHARED=ON and
CLANG_LINK_CLANG_DYLIB=ON
Summary: We were linking all the clang objects and shared libraries into 
libclang-cpp.so, which was causing the command line options to be 
registered twice.
Reviewers: beanz, mgorny
Reviewed By: beanz, mgorny
Subscribers: mgorny, cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D68520

Revert "[cmake] Fix clang builds with BUILD_SHARED=ON and
CLANG_LINK_CLANG_DYLIB=ON"
This reverts commit df839cfda09dbadc26b8be635f27da75f1f27190.
This change used cmake's list filter operation which was not added until
cmake 3.6.

[lldb/Reproducer] Disable buffering of stdout during replay
Different buffering behavior during capture and replay caused some of 
the shell tests to fail when run from a reproducer. By disabling stdout 
buffering we get a better approximation of how things get flushed during 
an regular debug session. There is a performance impact but since this 
only affects replay this is acceptable.

[IndVarSimplify] Teach IndVarSimplify to preserve MemorySSA.

[AArch64TTI] AArch64 supports NT vector stores through STNP.
This patch adds a custom implementation of isLegalNTStore to AArch64TTI 
that supports vector types that can be directly stored by STNP. Note 
that the implementation may not catch all valid cases (e.g. because the 
vector is a multiple of 256 and could be broken down to multiple valid
256 bit stores), but it is good enough for LV to vectorize loops with NT
stores, as LV only passes in a vector with 2 elements to check. LV seems
to also be the only user of isLegalNTStore.
We should also do the same for NT loads, but before that we need to 
ensure that we properly lower LDNP of vectors, similar to D72919.
Reviewers: dmgreen, samparker, t.p.northover, ab
Reviewed By: dmgreen
Differential Revision: https://reviews.llvm.org/D73158

[lldb/Reproducer] Mark some driver tests  as unsupported for lldb-repro
These test are checking for diagnostics printed by the driver. During 
replay we only replay the SB API calls made by the driver, so it's 
expected that these messages aren't displayed.

Replace old-style cast of null pointer with nullptr

[lldb/Test] Add check-lldb-repro target
This adds a new target check-lldb-repro which runs the shell tests with 
the lldb-repo utility. It runs the shell tests twice, once while 
capturing a reproducer and then again by replaying that reproducer.

[lldb/Test] Fix type in add_lit_testsuite
The new test suite should be called check-lldb-repro rather than 
check-lldb.

[lldb/Docs] Document testing strategies for the reproducers
Document the different ways we test the reproducers. This is mostly to 
describe the new check-lldb-repro target.

[RISCV] Fix evaluating %pcrel_lo against global and weak symbols
Summary: Previously, we would erroneously turn %pcrel_lo(label), where
label has a %pcrel_hi against a weak symbol, into %pcrel_lo(label +
offset), as evaluatePCRelLo would believe the target independent logic
was going to fold it. Moreover, even if that were fixed,
shouldForceRelocation lacks an MCAsmLayout and thus cannot evaluate the
%pcrel_hi fixup to a value and check the symbol, so we would then
erroneously constant-fold the
%pcrel_lo whilst leaving the %pcrel_hi intact. After D72197, this same 
sequence also occurs for symbols with global binding, which is triggered 
in real-world code.
Instead, as discussed in D71978, we introduce a new FKF_IsTarget flag to 
avoid these kinds of issues. All the resolution logic happens in one 
place, with no coordination required between RISCAsmBackend and 
RISCVMCExpr to ensure they implement the same logic twice. Although the 
implementation of %pcrel_hi can be left as target independent, we make 
it target dependent to ensure that they are handled identically to
%pcrel_lo, otherwise we risk one of them being constant folded but the 
other being preserved. This also allows us to properly support fixup 
pairs where the instructions are in different fragments.
Reviewers: asb, lenary, efriedma
Reviewed By: efriedma
Subscribers: arichardson, hiraditya, rbar, johnrusso, simoncook,
sabuasal, niosHD, kito-cheng, shiva0217, MaskRay, zzheng, edward-jones,
rogfer01, MartinMosbeck, brucehoult, the_o, rkruppe, PkmX, jocewei,
psnobl, benna, Jim, s.egerton, pzheng, sameer.abuasal, apazos,
luismarques, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D73211

[llvm/Transforms] Fix warning: private field 'MSSA' is not used

[test] Fix lld/test/ELF/riscv-pcrel-hilo-error.s after D73211

[LV] Fix predication for branches with matching true and false succs.
Currently due to the edge caching, we create wrong predicates for 
branches with matching true and false successors. We will cache the 
condition for the edge from the true successor, and then lookup the same 
edge (src and dst are the same) for the edge to the false successor.
If both successors match, the condition should always be true. At the 
moment, we cannot really create constant VPValues, but we can just 
create a true condition as X | !X. Later passes will clean that up.
Fixes PR44488.
Reviewers: rengolin, hsaito, fhahn, Ayal, dorit, gilr
Reviewed By: Ayal
Differential Revision: https://reviews.llvm.org/D73079

AMDGPU/GlobalISel: Remove redundant or patterns
These ended up with higher priority than or3 patterns in a future patch.
This also fixes the using VOP2 forms.

AMDGPU/GlobalISel: Fix generated wave64 checks
This inexplicably managed to pass locally without the updated wave64 
checks.

[libcxx] [test] Don't assert that moved-from containers with non-POCMA
allocators are empty.

[LICM] NFC. Remove AST caching infrastructure
Since LICM doesn't use AST caching any more (see D73081), this 
infrastructure is now obsolete and we can remove it.
Reviewers: asbirlea, fhahn, efriedma, reames
Reviewed-By: asbirlea
Differential Revision: https://reviews.llvm.org/D73084

[DWARF] Allow empty address range tables.
Empty address range tables are allowed by the DWARF standard; Moreover,
generating them is recommended as a best practice, see 
http://wiki.dwarfstd.org/index.php?title=Best_Practices#Generating_.debug_aranges_data
Differential Revision: https://reviews.llvm.org/D71931

[DWARF] Return Error from DWARFDebugArangeSet::extract().
This helps to detect and report parsing errors better. The patch follows
the ideas of LLDB's patches D59370 and D59381.
It adds tests for valid and some invalid cases. More checks and tests to
come. Note that the patch fixes validation of the Length field because
the value does not include the field itself.
The existing users are updated to show the error messages.
Differential Revision: https://reviews.llvm.org/D71875

[DWARF] Make dwarf::getUnitLengthFieldByteSize() constexpr. NFC.
This will help make some expressions in upcoming patches constexpr.
Differential Revision: https://reviews.llvm.org/D73036

[DWARF] Make dwarf::getDwarfOffsetByteSize() a free function. NFC.
This will help simplify code in upcoming patches and make some 
expressions constexpr.
Differential Revision: https://reviews.llvm.org/D73039

[DWARF] Support DWARF64 in DWARFDebugArangeSet.
This allows parsing Address Range Tables in the 64-bit DWARF format.
Differential Revision: https://reviews.llvm.org/D71876

[DWARF] Better detect errors in Address Range Tables.
The patch tries to cover most remaining cases of wrong data.
Differential Revision: https://reviews.llvm.org/D71932

[gn build] Port dcff3961c2d

Fix build bot failures.
Unfortunately, not all compilers allow using llvm_unreachable in a
constexpr function.

NFC. Remove obsolete SimpleAnalysis infrastructure
Apparently cache of AliasSetTrackers held by LICM was the only user of 
SimpleAnalysis infrastructure. Now, given that we no longer have that 
cache, this infrastructure is obsolete and, taking into account its 
nature, we don't want any new solutions to be based on it.
Reviewers: asbirlea, fhahn, efriedma, reames
Reviewed-By: asbirlea
Differential Revision: https://reviews.llvm.org/D73085

NFC. Add PR44320 IR test case.

[lldb/Test] Don't add a check-* target as dependency in
add_lit_testsuite
This causes the toplevel "test-depends" target, which should only build 
all the dependencies necessary for running tests, to suddenaly also run 
the check-lldb-repro-capture tests.
Instead add check-lldb-repro-capture as a dependency to check-lldb-repro 
with a separate explicit add_dependencies call.

[Concepts] Profile TypeConstraints in ProfileTemplateParameterList
Profile TypeConstraints in ProfileTemplateParameterList so we can
distinguish between partial specializations which differ in their
TemplateParameterList type constraints

[DWARF] Support 64-bit DWARF in .debug_pubnames and similar tables.
Differential Revision: https://reviews.llvm.org/D73103

Revert "[Concepts] Profile TypeConstraints in
ProfileTemplateParameterList"
This temporarily reverts commit 0e3ae353a47273825cd2f20f4777dcb5731cf8ec
because of a potential bug.

[Concepts] Profile TypeConstraints in ProfileTemplateParameterList
Profile TypeConstraints in ProfileTemplateParameterList so we can
distinguish between partial specializations which differ in their
TemplateParameterList type constraints.
Recommit, now profiling the IDC so that we can deal with situations
where the TemplateArgsAsWritten are nullptr (happens when canonicalizing
type constraints).

[DWARF] Get rid of DWARFDebugNames::HeaderPOD. NFC.
This structure was used to get the size of the fixed-size part of a Name 
Index header for 32-bit DWARF. It is unsuitable for 64-bit DWARF because 
the size of the unit length field is different.
Differential Revision: https://reviews.llvm.org/D73040

[DWARF] Eliminate the DWARFDebugNames::Header::Padding field.
The padding field is reserved for DWARF and does not contain any useful 
information. No need to read, store and report it.
Differential Revision: https://reviews.llvm.org/D73042

[SSAUpdater] Don't call ValueIsRAUWd upon single use replacement
It is incorrect to call ValueHandleBase::ValueIsRAUWd when only one use 
is replaced since it simply violates semantics of the callback and leads 
to bugs like PR44320.
Previously this call was used specifically to keep LICM's cache of 
AliasSetTrackers up to date across passes (as PR36801 showed, even for 
that purpose it didn't work properly), but since LICM doesn't have that 
cache anymore, we can safely remove this incorrect call with no 
repercussions.
This patch fixes https://bugs.llvm.org/show_bug.cgi?id=44320
Reviewers: asbirlea, fhahn, efriedma, reames
Reviewed-By: asbirlea
Differential Revision: https://reviews.llvm.org/D73089

[LLD][COFF] Enable linking of __declspec(selectany) symbols from Clang
and GCC
When annotating a symbol with __declspec(selectany), Clang assigns it 
comdat 2 while GCC assigns it comdat 3. This patch enables two object 
files that contain a __declspec(selectany) symbol, one created by gcc 
and the other by clang, to be linked together instead of issuing a 
duplicate symbol error.
Differential Revision: https://reviews.llvm.org/D73139

[llvm-exegesis] Restrict to allowed back-to-back instructions in
SerialSnippetGenerator.
Summary: Followup to D73161.
Reviewers: gchatelet, mstojanovic
Subscribers: tschuett, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D73256

[lldb][NFC] Rename ClangASTContext to TypeSystemClang
Summary: This commit renames ClangASTContext to TypeSystemClang to
better reflect what this class is actually supposed to do
(implement the TypeSystem interface for Clang). It also gets rid of the
very confusing situation that we have both a
`clang::ASTContext` and a `ClangASTContext` in clang (which sometimes
causes Clang people to think I'm fiddling with Clang's ASTContext when
I'm actually just doing LLDB work).
I also have plans to potentially have multiple clang::ASTContext
instances associated with one ClangASTContext so the ASTContext naming
will then become even more confusing to people.
Reviewers: #lldb, aprantl, shafik, clayborg, labath, JDevlieghere,
davide, espindola, jdoerfert, xiaobai
Reviewed By: clayborg, labath, xiaobai
Subscribers: wuzish, emaste, nemanjai, mgorny, kbarton, MaskRay,
arphaman, jfb, usaxena95, jingham, xiaobai, abidh, JDevlieghere,
lldb-commits
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D72684

[Object][test] - Remove readobj-elf-versioning.test and support files.
`readobj-elf-versioning.test` was added in rL152436 and checks how
llvm-readobj --dyn-syms prints versioned symbols. We test the same in
`llvm-readobj\ELF\dyn-symbols.test` currently.
This patch removes the test and 4 more support files from Inputs.
Differential revision: https://reviews.llvm.org/D73163

[llvm-readobj][test] - Add a check for --dyn-syms.
We have a `-dyn-symbols` option. It has a `--dyn-syms` alias that is not
tested in llvm-readobj tests currently.
There was a Object/readobj-elf-versioning.test where it is used, but
I've removed it in D73163. And also it is not the right place to test it
anyways.
Differential revision: https://reviews.llvm.org/D73164

[test] Avoid loop-unroll.c test getting confused by fadd in git revision
Differential Revision: https://reviews.llvm.org/D73162

[lldb][NFC] Delete empty file source/Host/linux/ProcessLauncherLinux.cpp
This was renamed in 816ae4b0dfac9a2bd964e8c4dae6dd7183ceb92a but it
seems the commit only emptied the file instead of deleting it.

Revert "[Concepts] Placeholder constraints and abbreviated templates"
This reverts commit e57a9abc4b01fa69fe81ace8df70517983b6cbac.
Parser/cxx2a-placeholder-type-constraint.cpp has MSan failures.
Present at 7b81c3f8793d30a4285095a9b67dcfca2117916c: 
http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap-msan/builds/17133/steps/check-clang%20msan/logs/stdio 
not present at eaa594f4ec54eba52b03fd9f1c789b214c66a753: 
http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap-msan/builds/17132/steps/check-clang%20msan/logs/stdio
Stack trace:
```
==57032==WARNING: MemorySanitizer: use-of-uninitialized-value
   #0 0xccfe016 in clang::AutoTypeLoc::getLocalSourceRange() const
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/include/clang/AST/TypeLoc.h:2036:19
   #1 0xcc56758 in CheckDeducedPlaceholderConstraints(clang::Sema&,
clang::AutoType const&, clang::AutoTypeLoc, clang::QualType)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaTemplateDeduction.cpp:4505:56
   #2 0xcc550ce in clang::Sema::DeduceAutoType(clang::TypeLoc,
clang::Expr*&, clang::QualType&, llvm::Optional<unsigned int>, bool)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaTemplateDeduction.cpp:4707:11
   #3 0xcc52407 in clang::Sema::DeduceAutoType(clang::TypeSourceInfo*,
clang::Expr*&, clang::QualType&, llvm::Optional<unsigned int>, bool)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaTemplateDeduction.cpp:4457:10
   #4 0xba38332 in
clang::Sema::deduceVarTypeFromInitializer(clang::VarDecl*,
clang::DeclarationName, clang::QualType, clang::TypeSourceInfo*,
clang::SourceRange, bool, clang::Expr*)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaDecl.cpp:11351:7
   #5 0xba3a8a9 in
clang::Sema::DeduceVariableDeclarationType(clang::VarDecl*, bool,
clang::Expr*)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaDecl.cpp:11385:26
   #6 0xba3c520 in clang::Sema::AddInitializerToDecl(clang::Decl*,
clang::Expr*, bool)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Sema/SemaDecl.cpp:11725:9
   #7 0xb39c498 in
clang::Parser::ParseDeclarationAfterDeclaratorAndAttributes(clang::Declarator&,
clang::Parser::ParsedTemplateInfo const&, clang::Parser::ForRangeInit*)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:2399:17
   #8 0xb394d80 in
clang::Parser::ParseDeclGroup(clang::ParsingDeclSpec&,
clang::DeclaratorContext, clang::SourceLocation*,
clang::Parser::ForRangeInit*)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:2128:21
   #9 0xb383bbf in
clang::Parser::ParseSimpleDeclaration(clang::DeclaratorContext,
clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&, bool,
clang::Parser::ForRangeInit*, clang::SourceLocation*)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:1848:10
   #10 0xb383129 in
clang::Parser::ParseDeclaration(clang::DeclaratorContext,
clang::SourceLocation&, clang::Parser::ParsedAttributesWithRange&,
clang::SourceLocation*)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/llvm/include/llvm/ADT/PointerUnion.h
   #11 0xb53a388 in
clang::Parser::ParseStatementOrDeclarationAfterAttributes(llvm::SmallVector<clang::Stmt*,
32u>&, clang::Parser::ParsedStmtContext, clang::SourceLocation*,
clang::Parser::ParsedAttributesWithRange&)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:221:13
   #12 0xb539309 in
clang::Parser::ParseStatementOrDeclaration(llvm::SmallVector<clang::Stmt*,
32u>&, clang::Parser::ParsedStmtContext, clang::SourceLocation*)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:106:20
   #13 0xb55610e in clang::Parser::ParseCompoundStatementBody(bool)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:1079:11
   #14 0xb559529 in
clang::Parser::ParseFunctionStatementBody(clang::Decl*,
clang::Parser::ParseScope&)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseStmt.cpp:2204:21
   #15 0xb33c13e in
clang::Parser::ParseFunctionDefinition(clang::ParsingDeclarator&,
clang::Parser::ParsedTemplateInfo const&,
clang::Parser::LateParsedAttrList*)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:1339:10
   #16 0xb394703 in
clang::Parser::ParseDeclGroup(clang::ParsingDeclSpec&,
clang::DeclaratorContext, clang::SourceLocation*,
clang::Parser::ForRangeInit*)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseDecl.cpp:2068:11
   #17 0xb338e52 in
clang::Parser::ParseDeclOrFunctionDefInternal(clang::Parser::ParsedAttributesWithRange&,
clang::ParsingDeclSpec&, clang::AccessSpecifier)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:1099:10
   #18 0xb337674 in
clang::Parser::ParseDeclarationOrFunctionDefinition(clang::Parser::ParsedAttributesWithRange&,
clang::ParsingDeclSpec*, clang::AccessSpecifier)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:1115:12
   #19 0xb334a96 in
clang::Parser::ParseExternalDeclaration(clang::Parser::ParsedAttributesWithRange&,
clang::ParsingDeclSpec*)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:935:12
   #20 0xb32f12a in
clang::Parser::ParseTopLevelDecl(clang::OpaquePtr<clang::DeclGroupRef>&,
bool)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/Parser.cpp:686:12
   #21 0xb31e193 in clang::ParseAST(clang::Sema&, bool, bool)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Parse/ParseAST.cpp:158:20
   #22 0x80263f0 in clang::FrontendAction::Execute()
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Frontend/FrontendAction.cpp:936:8
   #23 0x7f2a257 in
clang::CompilerInstance::ExecuteAction(clang::FrontendAction&)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/Frontend/CompilerInstance.cpp:965:33
   #24 0x8288bef in
clang::ExecuteCompilerInvocation(clang::CompilerInstance*)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/lib/FrontendTool/ExecuteCompilerInvocation.cpp:290:25
   #25 0xad44c2 in cc1_main(llvm::ArrayRef<char const*>, char const*,
void*)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/tools/driver/cc1_main.cpp:239:15
   #26 0xacd76a in ExecuteCC1Tool(llvm::ArrayRef<char const*>)
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/tools/driver/driver.cpp:325:12
   #27 0xacc9fd in main
/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm-project/clang/tools/driver/driver.cpp:398:12
   #28 0x7f7d82cdb2e0 in __libc_start_main
(/lib/x86_64-linux-gnu/libc.so.6+0x202e0)
   #29 0xa4dde9 in _start
(/b/sanitizer-x86_64-linux-bootstrap-msan/build/llvm_build_msan/bin/clang-11+0xa4dde9)
```

[llvm-exegesis] Allow the randomizer to fail nicely...
Summary:
... instead of crashing. On typical exmaple is when there are no
available registers.
Reviewers: gchatelet
Subscribers: tschuett, mstojanovic, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D73196

[mlir] Shrink-wrap anonymous namespaces around the classes it's supposed
to enclose. NFC.
The coding standards prefer smaller anonymous namespaces with free 
functions just being static and in the global namespace.

[NFC][DwarfDebug] Use proper analog GNU attribute for the pc address
The low_pc is analog to the DW_AT_call_return_pc, since it describes the
return address after the call. The DW_AT_call_pc is the address of the
call instruction, and we don't use it at the moment.
Differential Revision: https://reviews.llvm.org/D73173

[LLD] [COFF] Silence a GCC warning about an unused variable. NFC.

[SelectionDAG] Compute Known + Sign Bits - merge INSERT_SUBVECTOR
known/unknown index paths
Match the approach in SimplifyDemandedBits where we calculate the
demanded elts and then have a common path for the
ComputeKnownBits/ComputeNumSignBits call, additionally we only ever need
original demanded elts of the base vector even if the index is unknown.

[SelectionDAG] ComputeKnownBits - merge EXTRACT_VECTOR_ELT known/unknown
index paths
Match the approach in SimplifyDemandedBits/ComputeNumSignBits where we
calculate the demanded elts and then have a common path for the
ComputeKnownBits call.

[FileCheck] Strengthen error checks in unit tests
Summary: This commit adds error checking beyond UndefVarError and fix a
number of Error/Expected related idioms:
- use (EXPECT|ASSERT)_THAT_(ERROR|EXPECTED) instead of errorToBool or
 boolean operator
- ASSERT when a further check require the check to be successful to give
 a correct result
Reviewers: jhenderson, jdenny, probinson, grimar, arichardson, rnk
Reviewed By: jhenderson
Subscribers: llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D72914

[llvm-exegesis] Don't use unsupported aliasing instructions
Since some instruction types aren't allowed as the main instruction also 
don't allow them for aliasing instructions.
Differential Revision: https://reviews.llvm.org/D73220

[ARM,MVE] Revise immediate VBIC/VORR to look more like NEON.
Summary: In NEON, the immediate forms of VBIC and VORR are each
represented as a single MC instruction, which takes its immediate
operand already encoded in a NEON-friendly format: 8 data bits, plus
some control bits indicating how to expand them into a full vector.
In MVE, we represented immediate VBIC and VORR as four separate MC 
instructions each, for an 8-bit immediate shifted left by 0, 8, 16 or 24
bits. For each one, the value of the immediate operand is in the
'natural' form, i.e. the numerical value that would actually be BICed or
ORRed into each vector lane (and also the same value shown in assembly).
For example, MVE_VBICIZ16v4i32 takes an operand such as 0xab0000, which
NEON would represent as 0xab | (control bits << 8).
The MVE approach is superficially nice (it makes assembly input and 
output easy, and it's also nice if you're manually constructing 
immediate VBICs). But it turns out that it's better for isel if we make
the NEON and MVE instructions work the same, because the ARMISD::VBICIMM
and VORRIMM node types already encode their immediate into the NEON
format, so it's easier if we can just use it.
Also, this commit reduces the total amount of code rather than 
increasing it, which is surely an indication that it really is simpler 
to do it this way!
Reviewers: dmgreen, ostannard, miyuki, MarkMurrayARM
Reviewed By: dmgreen
Subscribers: kristof.beyls, hiraditya, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D73205

[ARM,MVE] Support immediate vbicq,vorrq,vmvnq intrinsics.
Summary: Immediate vmvnq is code-generated as a simple vector constant
in IR, and left to the backend to recognize that it can be created with
an MVE VMVN instruction. The predicated version is represented as a 
select between the input and the same constant, and I've added a 
Tablegen isel rule to turn that into a predicated VMVN. (That should be
better than the previous VMVN + VPSEL: it's the same number of 
instructions but now it can fold into an adjacent VPT block.)
The unpredicated forms of VBIC and VORR are done by enabling the same 
isel lowering as for NEON, recognizing appropriate immediates and 
rewriting them as ARMISD::VBICIMM / ARMISD::VORRIMM SDNodes, which I 
then instruction-select into the right MVE instructions (now that I've 
also reworked those instructions to use the same MC operand encoding). 
In order to do that, I had to promote the Tablegen SDNode instance
`NEONvorrImm` to a general `ARMvorrImm` available in MVE as well, and 
similarly for `NEONvbicImm`.
The predicated forms of VBIC and VORR are represented as a vector select
between the original input vector and the output of the unpredicated
operation. The main convenience of this is that it still lets me use the
existing isel lowering for VBICIMM/VORRIMM, and not have to write
another copy of the operand encoding translation code.
This intrinsic family is the first to use the `imm_simd` system I put 
into the MveEmitter tablegen backend. So, naturally, it showed up a bug
or two (emitting bogus range checks and the like). Fixed those, and
added a full set of tests for the permissible immediates in the existing
Sema test.
Also adjusted the isel pattern for `vmovlb.u8`, which stopped matching 
because lowering started turning its input into a VBICIMM. Now it 
recognizes the VBICIMM instead.
Reviewers: dmgreen, MarkMurrayARM, miyuki, ostannard
Reviewed By: dmgreen
Subscribers: kristof.beyls, hiraditya, cfe-commits, llvm-commits
Tags: #clang, #llvm
Differential Revision: https://reviews.llvm.org/D72934

[AArch64][SVE] Add first-faulting load intrinsic
Summary: Implements the llvm.aarch64.sve.ldff1 intrinsic and DAG combine
rules for first-faulting loads with sign & zero extends
Reviewers: sdesmalen, efriedma, andwar, dancgr, rengolin
Reviewed By: sdesmalen
Subscribers: tschuett, kristof.beyls, hiraditya, rkruppe, psnobl,
cameron.mcinally, cfe-commits, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D73025

Treat C# `using` as a control statement
Contributed by jbcoe!
Summary: Unless SpaceBeforeParensOptions is set to SBPO_Never, a space
will be put between `using` and `(` in C# code.
Reviewers: klimek, MyDeveloperDay, krasimir
Reviewed By: krasimir
Subscribers: MyDeveloperDay, cfe-commits
Tags: #clang-format, #clang
Differential Revision: https://reviews.llvm.org/D72144

[Alignement][NFC] Deprecate untyped CreateAlignedLoad
Summary: This is patch is part of a series to introduce an Alignment
type. See this thread for context:
http://lists.llvm.org/pipermail/llvm-dev/2019-July/133851.html See this
patch for the introduction of the type: https://reviews.llvm.org/D64790
Reviewers: courbet
Subscribers: arsenm, jvesely, nhaehnle, hiraditya, kerbowa, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D73260

[LoopRotate] add ability to repeat loop rotation until non-deoptimizing
exit is found
In case of loops with multiple exit where all-but-one exit are
deoptimizing it might happen that the first rotation will end up with
latch having a deoptimizing exit. This makes the loop unsuitable for
trip-count analysis (say, getLoopEstimatedTripCount) as well as for loop
transformations that know how to handle multple deoptimizing exits.
It pretty much means that canonical form in multple-deoptimizing-exits
case should be with non-deoptimizing exit at latch. Teach loop-rotation
to reach this canonical form by repeating rotation.
-loop-rotate-multi option introduced to control this behavior, currently
disabled by default.
Reviewers: skatkov, asbirlea, reames, fhahn Reviewed By: skatkov
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D73058

[SelectionDAG] Compute Known + Sign Bits - merge INSERT_VECTOR_ELT
known/unknown index paths
Match the approach in SimplifyDemandedBits where we calculate the
demanded elts and then have a common path for the
ComputeKnownBits/ComputeNumSignBits call.

[NFC][RDA] Make the interface const
Make all the public query methods const.

[gn build] Port 2f6987ba61c

[CodeGen] Make use of MachineInstrBuilder::getReg
Reviewers: arsenm
Subscribers: wdng, hiraditya, Petar.Avramovic, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D73262

Revert "[mlir] Add baseAttr to TypedArrayAttrBase."
This reverts commit eec36909c18b8788773abc95d199e6acde6eb42c.
This modeling is incorrect. baseAttr is intended for attribute 
decorators that are not backed by C++ attribute classes. It essentially 
says DerivedAttr isa BaseAttr, which is wrong for ArrayAttr classes. If
one needs to store the element type, it should be stored as a separate
filed in the tablegen class.

[tablegen] Emit string literals instead of char arrays
This changes the generated (Instr|Asm|Reg|Regclass)Name tables from this 
form:
   extern const char HexagonInstrNameData[] = {
     /* 0 */ 'G', '_', 'F', 'L', 'O', 'G', '1', '0', 0,
     /* 9 */ 'E', 'N', 'D', 'L', 'O', 'O', 'P', '0', 0,
     /* 18 */ 'V', '6', '_', 'v', 'd', 'd', '0', 0,
     /* 26 */ 'P', 'S', '_', 'v', 'd', 'd', '0', 0,
     [...]
   };
...to this:
    extern const char HexagonInstrNameData[] = {
     /* 0 */ "G_FLOG10\0"
     /* 9 */ "ENDLOOP0\0"
     /* 18 */ "V6_vdd0\0"
     /* 26 */ "PS_vdd0\0"
     [...]
   };
This should make debugging and exploration a lot easier for mortals, 
while providing a significant compile-time reduction for common
compilers.
To avoid issues with low implementation limits, this is disabled by 
default for visual studio or when cross-compiling.
To force output one way or the other, pass
`--long-string-literals=<bool>` to `tablegen`
Reviewers: mstorsjo, rnk
Subscribers: llvm-commit
Differential Revision: https://reviews.llvm.org/D73044

[ARM,MVE] Make the MVE intrinsics work in C++!
Summary: Apparently nobody has tried this in months of development. It
turns out that `FunctionDecl::getBuiltinID` will never consider a
function to be a builtin if it is in C++ and not extern "C". So none of
the function declarations in <arm_mve.h> are recognized as builtins when 
clang is compiling in C++ mode: it just emits calls to them as ordinary
functions, which then turn out not to exist at link time.
The trivial fix is to wrap most of arm_mve.h in an extern "C".
Added a test in clang/test/CodeGen/arm-mve-intrinsics which checks basic
functioning of the MVE header file in C++ mode. I've filled it with
copies of existing test functions from other files in that directory,
including a few moderately tricky cases of overloading (in particular
one that relies on the strict-polymorphism attribute added in D72518).
(I considered making //every// test in that directory compile in both C
and C++ mode and check the code generation was identical. But I think
that would increase testing time by more than the value it adds, and
also update_cc_test_checks gets confused when the output function name
varies between RUN lines.)
Reviewers: LukeGeeson, MarkMurrayARM, miyuki, dmgreen
Reviewed By: MarkMurrayARM
Subscribers: kristof.beyls, cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D73268

[VE][NFC] re-write RR* isel class using null_frag
Summary: Re-write RR* using null_frag to avoid duplication in upcoming
patches.
Reviewed By: arsenm
Differential Revision: https://reviews.llvm.org/D73259

[clang][CodeComplete] Make completion work after initializer lists
Summary: CodeCompletion was not being triggered after successfully
parsed initializer lists, e.g.
```cpp void foo(int, bool); void bar() {
 foo({1}^, false);
}
```
CodeCompletion would suggest the function foo as an overload candidate
up until the point marked with `^` but after that point we do not
trigger signature help since parsing succeeds.
This patch handles that case by failing in parsing expression lists
whenever we see a codecompletion token, in addition to getting an
invalid subexpression.
Reviewers: sammccall
Subscribers: cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D73177

Revert "Resubmit: [JumpThreading] Thread jumps through two basic blocks"
This reverts commit 53b68e676faf208b4a8f817e9bd4ddd522cc6006.
Our internal tests are showing breakage with this patch.

[VE] add, sub, left/right shift isel patterns
Summary: Add, sub, left/right shift isel patterns and tests for i32/i64
and fp32/fp64.
Reviewed By: arsenm
Differential Revision: https://reviews.llvm.org/D73207

[Dsymutil][Debuginfo][NFC] #4 Refactor dsymutil to separate DWARF
optimizing part.
Summary: The primary goal of this refactoring is to separate DWARF
optimizing part. So that it could be reused by linker or by any other
client. There was a thread on llvm-dev discussing the necessity of such
a refactoring:
http://lists.llvm.org/pipermail/llvm-dev/2019-September/135068.html.
This is a final part from series of patches for dsymutil. Previous
patches : D71068, D71839, D72476. This patch:
1. Creates lib/DWARFLinker interface :
   void addObjectFile(DwarfLinkerObjFile &ObjFile);
  bool link();
  void setOptions;
1. Moves all linking logic from tools/dsymutil/DwarfLinkerForBinary
  into lib/DWARFLinker. 2. Renames RelocationManager into
AddressesManager. 3. Remarks creation logic moved from separate parallel
execution
  into object file loading routine.
Testing: it passes "check-all" lit testing. MD5 checksum for clang .dSYM
bundle matches for the dsymutil with/without that patch.
Reviewers: JDevlieghere, friss, dblaikie, aprantl, jdoerfert
Reviewed By: JDevlieghere
Subscribers: merge_guards_bot, hiraditya, jfb, llvm-commits, probinson,
thegameg
Tags: #llvm, #debug-info
Differential Revision: https://reviews.llvm.org/D72915

Revert "[tablegen] Emit string literals instead of char arrays"
This reverts commit ce23515f5ab01161c98449d833b3ae013b553aa8.
That commit broke some builds on Windows: 
http://lab.llvm.org:8011/builders/clang-x64-windows-msvc/builds/13870

[Hexagon] Remove unused operand definitions: s10_0Imm and s10_6Imm

Fix GCC warning/error '-fpermission'. NFC.

[hip] Remove `-Werror=format-nonliteral`
Summary:
- It won't distinguish host and device code and trigger compilation
 failure on irrelevant code.
Reviewers: sameerds, yaxunl
Subscribers: cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D73224

[OPENMP]Fix use of local allocators in allocate clauses.
If local allocator was declared and used in the allocate clause, it was 
not captured in inner region. It leads to a compiler crash, need to 
capture the allocator declarator.

[OpenMP] change omp_atk_* and omp_atv_* enumerators to lowercase [NFC]
The OpenMP spec defines the OMP_ATK_* and OMP_ATV_* to be lowercase.
Differential Revision: https://reviews.llvm.org/D73248

[X86][AVX] Add AVX1/AVX2 ashr vector tests

[SelectionDAG] ComputeNumSignBits - add ISD::SUB demanded elts support

[NFC][ARM] Add test

AMDGPU: Check for other uses when looking through casted select
Fixes mesa regression on ext_transform_feedback-max-varyings

[Alignment][NFC] Use Align with CreateAlignedStore
Summary: This is patch is part of a series to introduce an Alignment
type. See this thread for context:
http://lists.llvm.org/pipermail/llvm-dev/2019-July/133851.html See this
patch for the introduction of the type: https://reviews.llvm.org/D64790
Reviewers: courbet, bollu
Subscribers: arsenm, jvesely, nhaehnle, hiraditya, kerbowa, cfe-commits,
llvm-commits
Tags: #clang, #llvm
Differential Revision: https://reviews.llvm.org/D73274

[X86][SSE] Add ComputeNumSignBits tests for (ADD (AND X, 1), -1) vectors

[SelectionDAG] ComputeNumSignBits - add ISD::ADD vector support
Add missing handling for (ADD (AND X, 1), -1) uniform vectors

clang-cl: Parse /QIntel-jcc-erratum
It appears to be a new flag, see 
https://github.com/MicrosoftDocs/cpp-docs/commit/c7ac1c2635a631c61d3bed9f12b31dee6d6716fe

GlobalISel: Use Register

AMDGPU/GlobalISel: Select V_ADD3_U32/V_XOR3_B32
The other 3-op patterns should also be theoretically handled, but 
currently there's a bug in the inferred pattern complexity.
I'm not sure what the error handling strategy should be for potential 
constant bus violations. I think the correct strategy is to never 
produce mixed SGPR and VGPR operands in a typical VOP instruction, which
will trivially avoid them. However, it's possible to still have hand
written MIR (or erroneously transformed code) with these operands. When
these fold, the restriction will be violated. We currently don't have
any verifiers for reg bank legality. For now, just ignore the
restriction.
It might be worth triggering a DAG fallback on verifier error.

[RDA] Skip debug values
Skip debug instructions when iterating through a block to find uses.
Differential Revision: https://reviews.llvm.org/D73273

[analyzer] Improve FuchsiaHandleChecker's diagnostic messages
Differential Revision: https://reviews.llvm.org/D73229

[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).
Resubmit after fixing MSAN failures caused by incomplete initialization
of AutoTypeLocs in TypeSpecLocFiller.
Differential Revision: https://reviews.llvm.org/D65042

[SelectionDAG] ComputeNumSignBits - add ISD::ADD demanded elts support

[X86] Add AVX512 tests for vector rotations

[X86] Add test showing failure to remove vector rotate by zero

[X86] LowerRotate - early out for vector rotates by zero

[mlir] Fix vectorize transform crashing on none-op operand

[SVE] Add SVE2 patterns for unpredicated multiply instructions
Summary: Add patterns for SVE2 unpredicated multiply instructions:
- mul, smulh, umulh, pmul, sqdmulh, sqrdmulh
Reviewers: sdesmalen, huntergr, efriedma, c-rhodes, kmclaughlin,
rengolin
Subscribers: tschuett, hiraditya, rkruppe, psnobl, llvm-commits, amehsan
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D72799

[openmp] Disable archer if LIBOMP_OMPT_SUPPORT is off
This fixed build failures due to missing ompt headers.
See https://bugs.gentoo.org/700762.
Differential Revision: https://reviews.llvm.org/D73249

[LoopUnroll] Avoid UB when converting from WeakVH to `Value *`
Calling `operator*` on a WeakVH with a null value yields a null 
reference, which is UB. Avoid this by implicitly converting the WeakVH 
to a `Value *` rather than dereferencing and then taking the address for
the type conversion.
Differential Revision: https://reviews.llvm.org/D73280

[ELF] Pass `Relocation` to relaxGot and
relaxTls{GdToIe,GdToLe,LdToLe,IeToLe}
These functions call relocateOne(). This patch is a prerequisite for 
making relocateOne() aware of `Symbol` (D73254).
Reviewed By: grimar, nickdesaulniers
Differential Revision: https://reviews.llvm.org/D73250

[AArch64][test] Fix tests after D72799

[AArch64][test] Fix MC/AArch64 tests after D72799

[IndVarSimplify] Fix for MemorySSA preserve.

[lldb] s/lldb/%lldb in another test
As explained in Pavel's previous commit message: %lldb is the proper 
substitution. Using "lldb" can cause us to execute the system lldb 
instead of the one we are testing. This happens at least in standalone 
builds.

[mlir] Add option to use custom base class for dialect in
LLVMIRIntrinsicGen.
Summary: LLVMIRIntrinsicGen is using LLVM_Op as the base class for
intrinsics. This works for LLVM intrinsics in the LLVM Dialect, but when
we are trying to convert custom intrinsics that originate from a custom 
LLVM dialect (like NVVM or ROCDL) these usually have a different
"cppNamespace" that needs to be applied to these dialect.
These dialect specific characteristics (like "cppNamespace") are
typically organized by creating a custom op (like NVVM_Op or ROCDL_Op)
that passes the correct dialect to the LLVM_OpBase class.
It seems natural to allow LLVMIRIntrinsicGen to take that into 
consideration when generating the conversion code from one of these 
dialect to a set of target specific intrinsics.
Reviewers: rriddle, andydavis1, antiagainst, nicolasvasilache, ftynse
Subscribers: jdoerfert, mehdi_amini, jpienaar, burmako, shauheen,
arpith-jacob, mgester, lucyrfox, aartbik, liufengdb, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D73233

[LoopIdiomRecognize] Teach LoopIdiomRecognize to preserve MemorySSA.

[WPD/VFE] Always emit vcall_visibility metadata for
-fwhole-program-vtables
Summary: First patch to support Safe Whole Program Devirtualization
Enablement, see RFC here:
http://lists.llvm.org/pipermail/llvm-dev/2019-December/137543.html
Always emit !vcall_visibility metadata under -fwhole-program-vtables, 
and not just for -fvirtual-function-elimination. The vcall visibility 
metadata will (in a subsequent patch) be used to communicate to WPD 
which vtables are safe to devirtualize, and we will optionally convert 
the metadata to hidden visibility at link time. Subsequent follow on 
patches will help enable this by adding vcall_visibility metadata to the 
ThinLTO summaries, and always emit type test intrinsics under
-fwhole-program-vtables (and not just for vtables with hidden 
visibility).
In order to do this safely with VFE, since for VFE all vtable loads must 
be type checked loads which will no longer be the case, this patch adds 
a new "Virtual Function Elim" module flag to communicate to GlobalDCE 
whether to perform VFE using the vcall_visibility metadata.
One additional advantage of using the vcall_visibility metadata to drive 
more WPD at LTO link time is that we can use the same mechanism to 
enable more aggressive VFE at LTO link time as well. The link time 
option proposed in the RFC will convert vcall_visibility metadata to 
hidden (aka linkage unit visibility), which combined with
-fvirtual-function-elimination will allow it to be done more 
aggressively at LTO link time under the same conditions.
Reviewers: pcc, ostannard, evgeny777, steven_wu
Subscribers: mehdi_amini, Prazek, hiraditya, dexonsmith, davidxl,
cfe-commits, llvm-commits
Tags: #clang, #llvm
Differential Revision: https://reviews.llvm.org/D71907

Include phabricator.uri in .arcconfig
conduit_uri was renamed to phabricator.uri and git-phab fails to load
.arcconfig without this field.
Differential Revision: https://reviews.llvm.org/D72960

[Sema] Sanity-check alignment requested via
`__attribute__((assume_aligned(imm)))`
Summary: For `__builtin_assume_aligned()`, we do validate that the
alignment is not greater than `536870912` (D68824), but we don't do that
for
`__attribute__((assume_aligned(N)))` attribute. I suspect we should.
Reviewers: erichkeane, aaron.ballman, hfinkel, rsmith, jdoerfert
Reviewed By: erichkeane
Subscribers: cfe-commits, llvm-commits
Tags: #llvm, #clang
Differential Revision: https://reviews.llvm.org/D72994

[Sema] Attempt to perform call-size-specific
`__attribute__((alloc_align(param_idx)))` validation
Summary:
`alloc_align` attribute takes parameter number, not the alignment
itself, so given **just** the attribute/function declaration we can't do
any sanity checking for said alignment.
However, at call site, given the actual `Expr` that is passed into that
parameter, we //might// be able to evaluate said `Expr` as Integer
Constant Expression, and perform the sanity checks. But since there is
no requirement for that argument to be an immediate, we may fail, and
that's okay.
However if we did evaluate, we should enforce the same constraints as
with
`__builtin_assume_aligned()`/`__attribute__((assume_aligned(imm)))`: 
said alignment is a power of two, and is not greater than our magic
threshold
Reviewers: erichkeane, aaron.ballman, hfinkel, rsmith, jdoerfert
Reviewed By: erichkeane
Subscribers: cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D72996

[IR] Attribute/AttrBuilder: use Value::MaximumAlignment magic constant
Summary: I initially encountered those assertions when trying to create 
this IR `alignment` attribute from clang's
`__attribute__((assume_aligned(imm)))`, because until D72994 there is no
sanity checking for the value of `imm`.
But even then, we have `llvm::Value::MaximumAlignment` constant (which
is `536870912`), which is enforced for clang attributes, and then there
are some other magical constant
(`0x40000000` i.e. `1073741824` i.e. `2 * 536870912`) in
`Attribute::getWithAlignment()`/`AttrBuilder::addAlignmentAttr()`.
I strongly suspect that `0x40000000` is incorrect, and that also should
be `llvm::Value::MaximumAlignment`.
Reviewers: erichkeane, hfinkel, jdoerfert, gchatelet, courbet
Reviewed By: erichkeane
Subscribers: hiraditya, cfe-commits, llvm-commits
Tags: #llvm, #clang
Differential Revision: https://reviews.llvm.org/D72998

[Codegen] If reasonable, materialize clang's `AssumeAlignedAttr` as
llvm's Alignment Attribute on call-site function return value
Summary: This should be mostly NFC - we still lower the same alignment 
knowledge to the IR. The main reasoning here is that this somewhat
improves readability of IR like this, and will improve test coverage in
upcoming patch.
Even though the alignment is guaranteed to always be an I-C-E, we don't
always materialize it as llvm's Alignment Attribute because: 1. There
may be a non-zero offset 2. We may be sanitizing for alignment
Note that if there already was an IR alignment attribute on return
value, we union them, and thus the alignment only ever rises.
Also, there is a second relevant clang attribute `AllocAlignAttr`, so
that is why `AbstractAssumeAlignedAttrEmitter` is templated.
Reviewers: erichkeane, jdoerfert, hfinkel, aaron.ballman, rsmith
Reviewed By: erichkeane
Subscribers: cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D73005

[Codegen] If reasonable, materialize clang's `AllocAlignAttr` as llvm's
Alignment Attribute on call-site function return value
Summary: Much like with the previous patch (D73005) with
`AssumeAlignedAttr` handling, results in mildly more readable IR, and
will improve test coverage in upcoming patch.
Note that in `AllocAlignAttr`'s case, there is no requirement for that
alignment parameter to end up being an I-C-E.
Reviewers: erichkeane, jdoerfert, hfinkel, aaron.ballman, rsmith
Reviewed By: erichkeane
Subscribers: cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D73006

[Sema] Don't disallow placing `__attribute__((alloc_align(param_idx)))`
on `std::align_val_t`-typed parameters
Summary: I kind-of understand why it is restricted to integer-typed
arguments, for general enum's the value passed is not nessesairly the
alignment implied, although one might say that user would know best.
But we clearly should whitelist `std::align_val_t`, which is just a thin
wrapper over `std::size_t`, and is the C++ standard way of specifying
alignment.
Reviewers: erichkeane, rsmith, aaron.ballman, jdoerfert
Reviewed By: erichkeane
Subscribers: cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D73019

AMDGPU: Fix ubsan error
Since register classes go up to 1024, 32 elements, all masks bits are 
needed and a 32-bit shift by 32 is illegal. We didn't have any 
instructions theoretically using a 32 element VGPR before 
d1dbb5e4718a8f845abf0783513a33a55429470b

Revert "[Sema] Attempt to perform call-size-specific
`__attribute__((alloc_align(param_idx)))` validation"
Likely makes bots angry.
This reverts commit c2a9061ac5166e48fe85ea2b6dbce9457c964958.

Revert "[Sema] Sanity-check alignment requested via
`__attribute__((assume_aligned(imm)))`"
Likely makes bots angry.
This reverts commit a4cfb15d15a8a353fe316f2a9fe1c8c6a6740ef1.
# Conflicts:
#	clang/lib/Sema/SemaDeclAttr.cpp

[clangd] Add C++20 concepts support to findExplicitReferences() and
semantic highlighting
Summary: Fixes https://github.com/clangd/clangd/issues/259
Subscribers: ilya-biryukov, MaskRay, jkorous, arphaman, kadircet,
usaxena95, cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D73124

[clangd] Add C++20 concepts support to TargetFinder
Subscribers: ilya-biryukov, MaskRay, jkorous, arphaman, kadircet,
usaxena95, cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D73140

[PDB] Simplify API for making section map, NFC
Prevents API misuse described in PR44495

[ELF] --no-dynamic-linker: don't emit undefined weak symbols to .dynsym
I felt really sad to push this commit for my selfish purpose to make 
glibc -static-pie build with lld. Some code constructs in glibc require 
R_X86_64_GOTPCREL/R_X86_64_REX_GOTPCRELX referencing undefined weak to 
be resolved to a GOT entry not relocated by R_X86_64_GLOB_DAT (GNU ld 
behavior), e.g.
csu/libc-start.c
 if (__pthread_initialize_minimal != NULL)
   __pthread_initialize_minimal ();
elf/dl-object.c
 void
 _dl_add_to_namespace_list (struct link_map *new, Lmid_t nsid)
 {
   /* We modify the list of loaded objects.  */
   __rtld_lock_lock_recursive (GL(dl_load_write_lock));
Emitting a GLOB_DAT will make the address equal &__ehdr_start (true 
value) and cause elf/ldconfig to segfault. glibc really should move away 
from weak references, which do not have defined semantics.
Temporarily special case --no-dynamic-linker.

Re-add documentation for -flax-vector-conversions= removed in
edd4398f4cd33a305afbca76ac4e6590e9337f4d.
The documentation remains correct despite the revert of the patch.

Partially revert "[IR] Attribute/AttrBuilder: use
Value::MaximumAlignment magic constant"
Apparently makes bots angry.
This reverts commit d096f8d306b2b16a25f65ffb70849ca7963a0dac.

[lldb/Commands] Fix, rename and document column number arg to breakpoint
set.
We were incorrectly parsing the -C argument to breakpoint set as the 
column breakpoint, even though according to the help this should be the 
breakpoint command. This fixes that by renaming the option to -u, adding 
it to help, and adding a test case.
Differential revision: https://reviews.llvm.org/D73284

Clang added a new feature to the ObjC compiler that will translate
method calls to commonly un-overridden methods into a function that
checks whether the method is overridden anywhere and if not directly
dispatches to the NSObject implementation.
That means if you do override any of these methods, "step-in" will not
step into your code, since we hit the wrapper function, which has no
debug info, and immediately step out again.
Add code to recognize these functions as "trampolines" and a thread plan
that will get us from the function to the user code, if overridden.
<rdar://problem/54404114>
Differential Revision: https://reviews.llvm.org/D73225

[CMake][NFC] Refactor iOS simulator/device test configuration generation
code for ASan.
Summary: The previous code hard-coded platform names but compiler-rt's
CMake build system actually already knows which Apple platforms ASan
supports.
This change uses this information to enumerate the different Apple 
platforms.
rdar://problem/58798733
Reviewers: kubamracek, yln
Subscribers: mgorny, #sanitizers, llvm-commits
Tags: #sanitizers, #llvm
Differential Revision: https://reviews.llvm.org/D73232

[CMake][NFC] Refactor iOS simulator/device test configuration generation
code for TSan.
Summary: The previous code hard-coded platform names but compiler-rt's
CMake build system actually already knows which Apple platforms TSan
supports.
This change uses this information to enumerate the different Apple 
platforms.
This change relies on the `get_capitalized_apple_platform()` function 
added in a previous commit.
rdar://problem/58798733
Reviewers: kubamracek, yln
Subscribers: mgorny, #sanitizers, llvm-commits
Tags: #sanitizers, #llvm
Differential Revision: https://reviews.llvm.org/D73238

[CMake] Refactor iOS simulator/device test configuration generation code
for LibFuzzer.
Summary: In order to do this `FUZZER_SUPPORTED_OS` had to be pulled out
of
`lib/fuzzer/CMakeLists.txt` and into the main config so we can use it 
from the `test/fuzzer/CMakeList.txt`. `FUZZER_SUPPORTED_OS` currently 
has the same value of `SANITIZER_COMMON_SUPPORTED_OS` which preserves 
the existing behaviour but this allows us in the future to adjust the 
supported platforms independent of `SANITIZER_COMMON_SUPPORTED_OS`. This 
mirrors the other sanitizers.
For non-Apple platforms `FUZZER_SUPPORTED_OS` is not defined and 
surprisingly this was the behaviour before this patch because
`SANITIZER_COMMON_SUPPORTED_OS` was actually empty. This appears to not
matter right now because the functions that take an `OS` as an argument
seem to ignore it on non-Apple platforms.
While this change tries to be NFC it is technically not because we now
generate an iossim config whereas previously we didn't. This seems like
the right thing to do because the build system was configured to compile
LibFuzzer for iossim but previously we weren't generating a lit test
config for it. The device/simulator testing configs don't run by default
anyway so this shouldn't break testing.
This change relies on the get_capitalized_apple_platform() function 
added in a previous commit.
rdar://problem/58798733
Reviewers: kubamracek, yln
Subscribers: mgorny, #sanitizers, llvm-commits
Tags: #sanitizers, #llvm
Differential Revision: https://reviews.llvm.org/D73243

Change internal_start_thread arguments to match pthread_create.
This avoids a CFI-unfriendly function pointer type cast in 
internal_start_thread.

[CUDA] Fix order of memcpy arguments in __shfl_*(<64-bit type>).
Wrong argument order resulted in broken shfl ops for 64-bit types.

[ThinLTO] Summarize vcall_visibility metadata
Summary: Second patch in series to support Safe Whole Program
Devirtualization Enablement, see RFC here: 
http://lists.llvm.org/pipermail/llvm-dev/2019-December/137543.html
Summarize vcall_visibility metadata in ThinLTO global variable summary.
Depends on D71907.
Reviewers: pcc, evgeny777, steven_wu
Subscribers: mehdi_amini, Prazek, inglorion, hiraditya, dexonsmith,
arphaman, ostannard, llvm-commits, cfe-commits, davidxl
Tags: #clang, #llvm
Differential Revision: https://reviews.llvm.org/D71911

[Concepts] Add ExpressionEvaluationContexts to instantiation of
constraints
Proper ExpressionEvaluationContext were not being entered when
instantiating constraint expressions, which caused assertion failures in
certain cases, including bug #44614.

AMDGPU/GlobalISel: Fix RegBanKSelect for llvm.amdgcn.exp.compr
This wasn't updated for the immarg handling change. We really need a 
verifier for this.

GlobalISel: Add MIPatternMatch for G_ICMP/G_FCMP

[Concepts] Implement P1616R1 - Using unconstrained template template
parameters with constrained templates
Summary: Allow unconstrained template template parameters to accept
constrainted templates as arguments.
Reviewers: rsmith
Subscribers: cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D73155

[IPSCCP] Use ParamState for arguments at call sites.
We currently use integer ranges to merge concrete function arguments. We
use the ParamState range for those, but we only look up concrete values
in the regular state. For concrete function arguments that are 
themselves arguments of the containing function, we can use the param 
state directly and improve the precision in some cases.
Besides improving the results in some cases, this is also a small step
towards switching to ValueLatticeElement, by allowing D60582 to be a
NFC.
Reviewers: efriedma, davide
Reviewed By: efriedma
Differential Revision: https://reviews.llvm.org/D71836

[mlir] [VectorOps] Implement vector tuple get folding
Summary: Rewrites get-i tup<a1,...,an> into ai
Reviewers: nicolasvasilache, rriddle, andydavis1
Reviewed By: nicolasvasilache, rriddle, andydavis1
Subscribers: merge_guards_bot, mehdi_amini, rriddle, jpienaar, burmako,
shauheen, antiagainst, arpith-jacob, mgester, lucyrfox, liufengdb,
llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D73213

[lldb/Test] Disable command-breakpoint-col.test on Windows
I guess PDB doesn't have column information?

[Clang][IFS][Test] Work around in-process cc1 ASAN issues #2.
Using the same strategy as c38e42527b21.
D69825 revealed (introduced?) a problem when building with ASan, and 
some memory leaks somewhere. More details are available in the original 
patch.
Looks like we missed one failing tests, this patch adds the workaround 
to this test as well.

[lldb/Test] Disallow using substituted binaries in shell test.
Explicitly disallow using lldb instead of %lldb in the shell tests. This 
is a clever trick that is used by Swift to achieve the same results.
Differential revision: https://reviews.llvm.org/D73289

[AArch64][GlobalISel] Fallback if the +strict-align target feature is
given.
Works around PR44246.

[LLDB] Fix the handling of unnamed bit-fields when parsing DWARF
We ran into an assert when debugging clang and performing an expression
on a class derived from DeclContext. The assert was indicating we were
getting the offsets wrong for RecordDeclBitfields. We were getting both
the size and offset of unnamed bit-field members wrong. We could fix
this case with a quick change but as I extended the test suite to
include more combinations we kept finding more cases that were being
handled incorrectly. A fix that handled all the new cases as well as the
cases already covered required a refactor of the existing technique.
Differential Revision: https://reviews.llvm.org/D72953

[Concepts] Deprecate -fconcepts-ts, enable Concepts under -std=c++2a
Now with concepts support merged and mostly complete, we do not need
-fconcepts-ts
(which was also misleading as we were not implementing the TS) and can
enable concepts features under C++2a. A warning will be generated if
users still attempt to use -fconcepts-ts.

[tests] Use host-based XFAIL for test/MC/AMDGPU/hsa-gfx10-v3.s
Summary: This patch applies D60551 to an additional file. In particular,
the test is currently marked XFAIL for a number of big-endian targets;
however, the failure is actually dependent on the host endianness
instead. The test actually specifies a specific target triple.
Reviewers: rampitec, xingxue, daltenty
Reviewed By: rampitec
Subscribers: kzhuravl, jvesely, wdng, nhaehnle, yaxunl, dstuttard, tpr,
t-tye, fedor.sergeev, kerbowa, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D73192

[NFC][ScopBuilder] Move RecordedAssumptions vector to ScopBuilder
Scope of changes:
1) Moved RecordedAssumptions vector to ScopBuilder. RecordedAssumptions
are used only for Scop constructions. 2) Moved definition of
RecordedAssumptionsTy to ScopHelper. It is required both by ScopBuilder
and SCEVAffinator. 3) Add new function recordAssumption to ScopHelper.
One of its argument is a reference to RecordedAssumption vector. This
function is used by ScopBuilder and SCEVAffinator. 4) All
RecordedAssumptions are created by ScopBuilder. isl::pw_aff objects for
corresponding SCEVs are created inside ScopBuilder. Scop functions do
not record any assumptions. Scop can use isl::pw_aff objects which were
created by ScopBuilder. 5) Removed functions for handling
RecordedAssumptions from Scop class. 6) Removed constness from
getScopArrayInfo functions. 7) Replaced SCEVVisitor struct from
SCEVAffinator with taylored version, which allow to pass pointer to
RecordedAssumptions as function argument.
Differential Revision: https://reviews.llvm.org/D68056

[mlir] [VectorOps] fixed minor typos in vector ops doc
Summary: Rationale: Some examples were using "offsets : [0, 2]" syntax
which should use a "=" instead. The same examples were referring to the
integer attribute array as k-dimensional, which is a bit confusing (it
is 1-dimensional, with k elements). Changed to "k-sized".
Reviewers: nicolasvasilache, andydavis1, ftynse
Reviewed By: nicolasvasilache
Subscribers: merge_guards_bot, mehdi_amini, rriddle, jpienaar, burmako,
shauheen, antiagainst, arpith-jacob, mgester, lucyrfox, liufengdb,
llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D73293

[AArch64][GlobalISel] Remove duplicate attribute lookup code that was
supposed to be cached. NFC.
When I cached this a long time ago it seems I forgot to remove the
locally declared variable of the same name in select(), so the caching
wasn't having any compile time benefit. Doh.

[MS] Overhaul how clang passes overaligned args on x86_32
MSVC 2013 would refuse to pass highly aligned things (typically vectors 
and aggregates) by value. Users would receive this error:
 t.cpp(11) : error C2719: 'w': formal parameter with
__declspec(align('32')) won't be aligned
 t.cpp(11) : error C2719: 'q': formal parameter with
__declspec(align('32')) won't be aligned
However, in MSVC 2015, this behavior was changed, and highly aligned 
things are now passed indirectly. To avoid breaking backwards 
incompatibility, objects that do not have a *required* high alignment
(i.e. double) are still passed directly, even though they are not 
naturally aligned. This change implements the new behavior of passing 
things indirectly.
The new behavior is:
- up to three vector parameters can be passed in [XYZ]MM0-2
- remaining arguments with required alignment greater than 4 bytes are
 passed indirectly
Previously, MSVC never passed things truly indirectly, meaning clang 
would always apply the byval attribute to indirect arguments. We had to 
go to the trouble of adding inalloca so that non-trivially copyable C++ 
types could be passed in place without copying the object 
representation. When inalloca was added, we asserted that all arguments 
passed indirectly must use byval. With this change, that assert no 
longer holds, and I had to update inalloca to handle that case. The 
implicit sret pointer parameter was already handled this way, and this 
change generalizes some of that logic to arguments.
There are two cases that this change leaves unfixed: 1. objects that are
non-trivially copyable *and* overaligned 2. vectorcall + inalloca +
vectors
For case 1, I need to touch C++ ABI code in MicrosoftCXXABI.cpp, so I 
want to do it in a follow-up.
For case 2, my fix is one line, but it will require updating IR tests to 
use lots of inreg, so I wanted to separate it out.
Related to D71915 and D72110
Fixes most of PR44395
Reviewed By: rjmccall, craig.topper, erichkeane
Differential Revision: https://reviews.llvm.org/D72114

[Utils] Use WeakTrackingVH in vector used as scratch storage.
The utility method RecursivelyDeleteTriviallyDeadInstructions receives 
as input a vector of Instructions, where all inputs are valid 
instructions. This same vector is used as a scratch storage (per the 
header comment) to recursively delete instructions. If an instruction is 
added as an operand of multiple other instructions, it may be added
twice, then deleted once, then the second reference in the vector is
invalid. Switch to using a Vector<WeakTrackingVH>. This change
facilitates a clean-up in LoopStrengthReduction.

[LTO/WPD] Enable aggressive WPD under LTO option
Summary: Third part in series to support Safe Whole Program
Devirtualization Enablement, see RFC here: 
http://lists.llvm.org/pipermail/llvm-dev/2019-December/137543.html
This patch adds type test metadata under -fwhole-program-vtables, even
for classes without hidden visibility. It then changes WPD to skip 
devirtualization for a virtual function call when any of the compatible 
vtables has public vcall visibility.
Additionally, internal LLVM options as well as lld and gold-plugin 
options are added which enable upgrading all public vcall visibility to
linkage unit (hidden) visibility during LTO. This enables the more 
aggressive WPD to kick in based on LTO time knowledge of the visibility 
guarantees.
Support was added to all flavors of LTO WPD (regular, hybrid and 
index-only), and to both the new and old LTO APIs.
Unfortunately it was not simple to split the first and second parts of 
this part of the change (the unconditional emission of type tests and 
the upgrading of the vcall visiblity) as I needed a way to upgrade the 
public visibility on legacy WPD llvm assembly tests that don't include 
linkage unit vcall visibility specifiers, to avoid a lot of test churn.
I also added a mechanism to LowerTypeTests that allows dropping type 
test assume sequences we now aggressively insert when we invoke 
distributed ThinLTO backends with null indexes, which is used in testing 
mode, and which doesn't invoke the normal ThinLTO backend pipeline.
Depends on D71907 and D71911.
Reviewers: pcc, evgeny777, steven_wu, espindola
Subscribers: emaste, Prazek, inglorion, arichardson, hiraditya, MaskRay,
dexonsmith, dang, davidxl, cfe-commits, llvm-commits
Tags: #clang, #llvm
Differential Revision: https://reviews.llvm.org/D71913

[Attributor][FIX] Store alignment only holds for the pointer value
We accidentally used the store alignment for the value operand as well, 
which is incorrect and crashed the SPASS application in the test suite.

[Attributor] `byval` arguments are always `noalias`
`byval` introduces a local copy of the argument. That copy cannot alias 
anything.

[Attributor][NFC] Fix spelling

[Attributor][NFC] Add an assertion

[Attributor][FIX][Alignment] Do not report a change if there was none
If alignment was manifested but it is actually only as good as the 
data-layout provided one we should not report it as a change.
For testing purposes we still manifest the information.

[Concepts] Make constraint expressions unevaluated until satisfaction
checking
As per P1980R0, constraint expressions are unevaluated operands, and
their constituent atomic constraints only become constant evaluated
during satisfaction checking.
Change the evaluation context during parsing and instantiation of
constraints to unevaluated.

[LoopStrengthReduce] Reuse utility method to clean dead instructions.
[NFCI]
Create a utility wrapper for the
RecursivelyDeleteTriviallyDeadInstructions utility method, which sets to
nullptr the instructions that are not trivially dead. Use the new method
in LoopStrengthReduce. Alternative: add a bool to the same method; this
option adds a marginal amount of overhead to the other callers, and the
method needs to be updated to return a bool status when it
removes/doesn't remove instructions.

[clang-tidy] Add clang-tidy headers to clang distribution
Summary: Clang releases include static libraries for clang-tidy but
corresponding headers are missing in the tarball so these libraries are
almost useless. Clang-tidy libraries can be useful for build custom
clang-tidy with custom checks outside of llvm repo.
List of clang-tidy libraries included in clang 9.0.1 release:
   lib/libclangTidyMPIModule.a
   lib/libclangTidyPlugin.a
   lib/libclangTidyBoostModule.a
   lib/libclangTidyCERTModule.a
   lib/libclangTidyAndroidModule.a
   lib/libclangTidyPortabilityModule.a
   lib/libclangTidyPerformanceModule.a
   lib/libclangTidyOpenMPModule.a
   lib/libclangTidyBugproneModule.a
   lib/libclangTidyZirconModule.a
   lib/libclangTidyCppCoreGuidelinesModule.a
   lib/libclangTidyGoogleModule.a
   lib/libclangTidyUtils.a
   lib/libclangTidyHICPPModule.a
   lib/libclangTidyModernizeModule.a
   lib/libclangTidyLLVMModule.a
   lib/libclangTidyAbseilModule.a
   lib/libclangTidyReadabilityModule.a
   lib/libclangTidyFuchsiaModule.a
   lib/libclangTidyMiscModule.a
   lib/libclangTidy.a
   lib/libclangTidyObjCModule.a
Reviewers: smeenai, jdoerfert, alexfh, hokein, aaron.ballman
Subscribers: mgehre, mgorny, xazax.hun, cfe-commits
Tags: #clang-tools-extra, #clang
Differential Revision: https://reviews.llvm.org/D73236

Fix bot failure from 59733525d37cf9ad88b5021b33ecdbaf2e18911c
Fix bot failure by loosening up the register matching on new test: 
http://lab.llvm.org:8011/builders/clang-x86_64-debian-new-pass-manager-fast/builds/2423

[lldb/Util] Use md5 instead of python's hash function.
Because of the way the Python hash function works, it's not guaranteed 
to be the same. This was causing a lot of reproducers to be generated 
for the same tests, even though the CWD or arguments didn't change. 
Switching to an MD5 hash should fix that.

[Attributor][NFC] Do not (try to) simplify void values
We might accidentally ask AAValueSimplify to simplify a void value. That 
can lead to very interesting, and very wrong, results. We now handle 
this case gracefully.

[Attributor][FIX] Handle non-pointers when following uses
When we follow uses, e.g., in AAMemoryBehavior or AANoCapture, we need 
to make sure the value is a pointer before we ask for abstract 
attributes only valid for pointers. This happens because we follow 
pointers through calls that do not capture but may return the value.