Changes

[lldb][NFC] Migrate to raw_ostream in Module::GetDescription

[yaml2obj][test] - Remove excessive symtab-shinfo.yaml.
The same testing is performed in `implicit-sections-info.yaml`: 
https://github.com/llvm-mirror/llvm/blob/master/test/tools/yaml2obj/implicit-sections-info.yaml
Differential revision: https://reviews.llvm.org/D70957

[lldb][NFC] Extract single member parsing out of
DWARFASTParserClang::ParseChildMembers
ParseChildMembers does a few things, only one part is actually parsing a
single member. This extracts the member parsing logic into its own
function.
This commit just moves the code as-is into its own function and forwards
the parameters/ local variables to it, which means it should be NFC.
The only actual changes to the code are replacing 'break's (and one very
curious 'continue' that behaves like a 'break') with 'return's.

[SelectionDAG] Expand nnan FMINNUM/FMAXNUM to select sequence
InstCombine may synthesize FMINNUM/FMAXNUM nodes from fcmp+select 
sequences (where the fcmp is marked nnan).  Currently, if the target
does not otherwise handle these nodes, they'll get expanded to libcalls
to fmin/fmax.  However, these functions may reside in libm, which may
introduce a library dependency that was not originally present in the
source code, potentially resulting in link failures.
To fix this problem, add code to TargetLowering::expandFMINNUM_FMAXNUM 
to expand FMINNUM/FMAXNUM to a compare+select sequence instead of the 
libcall. This is done only if the node is marked as "nnan"; in this
case, the expansion to compare+select is always correct. This also
suffices to catch all cases where FMINNUM/FMAXNUM was synthesized as
above.
Differential Revision: https://reviews.llvm.org/D70965

[DWARFDebugRnglists] Add a callback-based version of the
getAbsoluteRanges function
Summary: The dump() function already accepts a callback. This makes 
getAbsoluteRanges do the same. The existing DWARFUnit overload is 
implemented on top of the new function.
This enables usage of the debug_rnglists parser from within lldb (which 
has it's own dwarf parser).
Reviewers: dblaikie, JDevlieghere, aprantl
Subscribers: hiraditya, probinson, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D70952

[DWARFDebugLoclists] Add support for other DW_LLE encodings
Summary: lldb's loclists parser has support for DW_LLE_start_end(x)
encodings. To avoid regressing when switching the implementation to
llvm's, I add parsing support for all previously unsupported location
list encodings.
Reviewers: dblaikie, JDevlieghere, aprantl, SouraVX
Subscribers: hiraditya, probinson, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D70949

[lldb] s/FileSpec::Equal/FileSpec::Match
Summary: The FileSpec class is often used as a sort of a pattern -- one
specifies a bare file name to search, and we check if in matches the
full file name of an existing module (for example).
These comparisons used FileSpec::Equal, which had some support for it
(via the full=false argument), but it was not a good fit for this job.
For one, it did a symmetric comparison, which makes sense for a function 
called "equal", but not for typical searches (when searching for
"/foo/bar.so", we don't want to find a module whose name is just
"bar.so"). This resulted in patterns like:
   if (FileSpec::Equal(pattern, file, pattern.GetDirectory())) which
would request a "full" match only if the pattern really contained a
directory. This worked, but the intended behavior was very unobvious.
On top of that, a lot of the code wanted to handle the case of an
"empty" pattern, and treat it as matching everything. This resulted in 
conditions like:
   if (pattern && !FileSpec::Equal(pattern, file,
pattern.GetDirectory()) which are nearly impossible to decipher.
This patch introduces a FileSpec::Match function, which does exactly 
what most of FileSpec::Equal callers want, an asymmetric match between a
"pattern" FileSpec and a an actual FileSpec. Empty paterns match 
everything, filename-only patterns match only the filename component.
I've tried to update all callers of FileSpec::Equal to use a simpler 
interface. Those that hardcoded full=true have been changed to use 
operator==. Those passing full=pattern.GetDirectory() have been changed 
to use FileSpec::Match.
There was also a handful of places which hardcoded full=false. I've 
changed these to use FileSpec::Match too. This is a slight change in 
semantics, but it does not look like that was ever intended, and it was 
more likely a result of a misunderstanding of the "proper" way to use 
FileSpec::Equal.
[In an ideal world a "FileSpec" and a "FileSpec pattern" would be two 
different types, but given how widespread FileSpec is, it is unlikely 
we'll get there in one go. This at least provides a good starting point 
by centralizing all matching behavior.]
Reviewers: teemperor, JDevlieghere, jdoerfert
Subscribers: emaste, lldb-commits
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D70851

[lldb/Editline] Fix a -Wreturn-type warning with gcc

[lldb] Add test for Stream::Address and Stream::AddressRange
I'm refactoring those functions, so we should have some tests for them
before doing that.

[lldb] Remove FileSpec(FileSpec*) constructor
This constructor was the cause of some pretty weird behavior. Remove it, 
and update all code to properly dereference the argument instead.

[lldb] s/assertTrue/assertEqual in TestStepTarget.py
this improves error messages.

[APFloat] Prevent construction of APFloat with Semantics and FP value
Constructor invocations such as `APFloat(APFloat::IEEEdouble(), 0.0)` 
may seem like they accept a FP (floating point) value, but the overload 
they reach is actually the `integerPart` one, not a `float` or `double` 
overload (which only exists when `fltSemantics` isn't passed).
This may lead to possible loss of data, by the conversion from `float` 
or `double` to `integerPart`.
To prevent future mistakes, a new constructor overload, which accepts 
any FP value and marked with `delete`, to prevent its usage.
Fixes PR34095.
Differential Revision: https://reviews.llvm.org/D70425

[lldb] Remove some (almost) unused Stream::operator<<'s
llvm::raw_ostream provides equivalent functionality.

[yaml2obj] - Make DynamicSymbols to be Optional<> too.
We already have Symbols property to list regular symbols and it is
currently Optional<>. This patch makes DynamicSymbols to be optional 
too. With this there is no need to define a dummy symbol anymore to
trigger creation of the .dynsym and it is now possible to define an
empty .dynsym using just the following line:
DynamicSymbols: []
(it is important to have when you do not want to have dynamic symbols, 
but want to have a .dynsym)
Now the code is consistent and it helped to fix a bug: previously we did
not report an error when both Content/Size and an empty 
Symbols/DynamicSymbols list were specified.
Differential revision: https://reviews.llvm.org/D70956

AMDGPU: Avoid folding 2 constant operands into an SALU operation
Summary: Catch the (admittedly unusual) case where SIFoldOperands
attempts to fold 2 constant operands into the same SALU operation, with
neither operand able to be encoded as an inline constant.
Change-Id: Ibc48d662c9ffd8bbacd154976b0b1c257ace0927
Subscribers: arsenm, kzhuravl, jvesely, wdng, nhaehnle, yaxunl, tpr,
t-tye, hiraditya, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D70896

[NFC] Use default case in EVT::getEVTString
Summary: The default case handles the majority of MVTs so most of the
individual cases can be removed. Also added a case for floating point
types.
Reviewed By: sdesmalen
Differential Revision: https://reviews.llvm.org/D70955

[AArch64TTI] Compute imm materialization cost for AArch64 intrinsics
Currently, getIntImmCost returns TCC_Free for almost all intrinsics. For
most AArch64 specific intrinsics however, it looks like integer 
constants cannot be folded into most of them (at least the ones I
checked).
Unless we know that we can fold integer operands with the intrinsic, we 
handle more cases correctly by returning the cost to materialize the 
immediate than return TCC_Free.
Reviewers: SjoerdMeijer, dmgreen, t.p.northover, ributzka
Reviewed By: SjoerdMeijer
Differential Revision: https://reviews.llvm.org/D70669

[clangd] Add no delayed templates to outline tests

Add debug output to MipsDelaySlotFiller pass
Summary: I was tracking down a code-generation bug in this pass and
found that the added output was useful. It is also helpful to find out
why a delay slot could not be filled even though there is clearly a
valid instruction (which appears to mostly be caused by CFI
instructions).
Reviewers: atanasyan
Reviewed By: atanasyan
Subscribers: merge_guards_bot, sdardis, hiraditya, jrtc27, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D70940

MipsDelaySlotFiller: Don't move BUNDLE instructions into the delay slot
Summary: In our CHERI fork we use BUNDLE instructions to ensure that a 
three-instruction sequence to generate a program-counter-relative value
is emitted without reordering or insertions (since that would break the
32-bit offset computation). This sequence is created in MipsExpandPseudo
and we use finalizeBundle() to create the BUNDLE instruction.
However, the delay slot filler currently breaks this pattern since the
BUNDLE will be removed and so all instructions are moved into the delay
slot. Since the delay slot only executes the first instruction, this
results in incorrect computations (and run-time crashes) if the branch
is taken.
The original test cases uses CHERI instructions, so for the test case
here I simple filled a BUNDLE with a no-op DADDiu $sp_64, -16 and DADDiu
$sp_64, 16.
Reviewers: atanasyan
Reviewed By: atanasyan
Subscribers: merge_guards_bot, sdardis, hiraditya, jrtc27, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D70944

Handle BUNDLE instructions in MipsAsmPrinter
Summary: In our CHERI fork we use BUNDLE instructions to ensure that a 
three-instruction sequence to generate a program-counter-relative value
is emitted without reordering or insertions (since that would break the
32-bit offset computation).
Currently MipsAsmPrinter asserts when it encounters a pseudo
instruction. To handle BUNDLE we can simply skip the instruction which
will then make EmitInstruction() process the contents of the bundle in
order.
Reviewers: atanasyan
Reviewed By: atanasyan
Subscribers: merge_guards_bot, sdardis, hiraditya, jrtc27, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D70945

Allow negative offsets in MipsMCInstLower::LowerOperand
Summary: We rely on this in our CHERI backend to address the GOT by
generating a
$pc-relative addresses. For this we emit the following code sequence:
lui $1, %pcrel_hi(_CHERI_CAPABILITY_TABLE_-8) daddiu $1, $1,
%pcrel_lo(_CHERI_CAPABILITY_TABLE_-4) cgetpccincoffset $c1, $1
However, without this change the addend is implicitly converted to 
UINT32_MAX and an invalid pointer value is generated.
Reviewers: atanasyan
Reviewed By: atanasyan
Subscribers: merge_guards_bot, sdardis, hiraditya, jrtc27, llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D70953

[SimpleLoopUnswitch] Invalidate the topmost loop with ExitBB as exiting.
SCEV caches the exiting blocks when computing exit counts. In 
SimpleLoopUnswitch, we split the exit block of the loop to unswitch.
Currently we only invalidate the loop containing that exit block, but if 
that block is the exiting block for a parent loop, we have stale cache 
entries. We have to invalidate the top-most loop that contains the exit 
block as exiting block. We might also be able to skip invalidating the 
loop containing the exit block, if the exit block is not an exiting 
block of that loop.
There are also 2 more places in SimpleLoopUnswitch, that use a similar 
problematic approach to get the loop to invalidate. If the patch makes 
sense, I will also update those places to a similar approach (they deal 
with multiple exit blocks, so we cannot directly re-use 
getTopMostExitingLoop).
Fixes PR43972.
Reviewers: skatkov, reames, asbirlea, chandlerc
Reviewed By: asbirlea
Differential Revision: https://reviews.llvm.org/D70786

[clangd] Remove the hanging lit exit-signal.test.
The test was introduced in 
https://github.com/llvm/llvm-project/commit/19ac0eaf07e60173baa7ee77fa11568c30b87455.
The test keeps hanging after running "check-clangd", remove it now and
will add it back later after investigations.

[AMDGPU][MC] Remove duplicate code introduced in r359316.

[AArch64][SVE] Implement reversal intrinsics
Summary: Adds intrinsics for the following:
    * rbit
   * revb
   * revh
   * revw
Patterns are also defined to map the 'llvm.bswap.*' intrinsic to the SVE 
revb instruction.
Reviewers: sdesmalen, huntergr, dancgr, rengolin, efriedma, rovka
Reviewed By: sdesmalen
Subscribers: tschuett, kristof.beyls, hiraditya, rkruppe, psnobl,
llvm-commits
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D70960

Actually delay processing DelayedDllExportClasses until the outermost
class is finished (PR40006)
This was already the intention of DelayedDllExportClasses, but code such
as this would break it:
template<typename> struct Tmpl {}; struct Outer {
   struct Inner {
       __declspec(dllexport) Inner() = default;
       unsigned int x = 0;
   };
   Tmpl<Inner> y;
};
ActOnFinishCXXNonNestedClass() would get called when the instantiation
of Templ<Inner> is finished, even though the compiler is still not
finished with Outer, causing the compile fail.
This hooks into Sema::{Push,Pop}ParsingClass() to avoid calling 
ActOnFinishCXXNonNestedClass() for template instantiations while a class
is being parsed.
Differential revision: https://reviews.llvm.org/D70905

[OpenCL] Allow addr space qualifiers on lambda call expressions
The addr space qualifier can be added optionally for lambdas after the
attributes. They will alter the default addr space of lambda call
operator that is in generic address space by default for OpenCL.
Syntax:
[ captures ] ( params ) specifiers exception attr opencl_addrspace
                   -> ret { body }
Example:
[&] (int i) mutable __global { ... };
On the call into lambda a compatibility check will be performed to 
determine whether address space of lambda object and its call operator 
are compatible. This will follow regular addr space conversion rules and
there will be no difference to how addr spaces work in method 
qualifiers.
Tags: #clang
Differential Revision: https://reviews.llvm.org/D70242

[NFC][InstCombine] Update sub-of-negatible.ll test

[lldb] Fix macOS build by replacing nullptr with FileSpec()
Before we had a implicit conversion from nullptr to FileSpec which was
thankfully removed.

[clangd] register cuda language activation event and activate for .cuh
files
Patch by Paul Taylor!
Reviewers: hokein
Reviewed By: hokein
Subscribers: jkorous, arphaman, kadircet, usaxena95, cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D70041

[Support] add vfs support for ExpandResponseFiles
Summary: add vfs support for `ExpandResponseFiles`.
Patch By: liu hui(@lh123)
Reviewers: kadircet, espindola, alexshap, rupprecht, jhenderson
Reviewed By: kadircet
Subscribers: mgorny, sammccall, merge_guards_bot, emaste, sbc100,
arichardson, hiraditya, aheejin, jakehehrlich, MaskRay, rupprecht,
seiya, cfe-commits, llvm-commits
Tags: #clang, #llvm
Differential Revision: https://reviews.llvm.org/D70769

[clang][Tooling] Add support for .rsp files in compile_commands.json
Summary: Add support for .rsp files.
Fixes https://github.com/clangd/clangd/issues/81
Patch By: liu hui(@lh123)
Reviewers: sammccall, ilya-biryukov, hokein, kadircet
Reviewed By: kadircet
Subscribers: merge_guards_bot, mgorny, MaskRay, jkorous, arphaman,
kadircet, usaxena95, cfe-commits
Tags: #clang-tools-extra, #clang
Differential Revision: https://reviews.llvm.org/D70222

[llvm][Support] Take in CurrentDirectory as a parameter in
ExpandResponseFiles
Summary: This is a follow-up to D70769 and D70222, which allows
propagation of current directory down to ExpandResponseFiles for
handling of relative paths.
Previously clients had to mutate FS to achieve that, which is not
thread-safe and can even be thread-hostile in the case of real file
system.
Reviewers: sammccall
Subscribers: hiraditya, cfe-commits, llvm-commits
Tags: #clang, #llvm
Differential Revision: https://reviews.llvm.org/D70857

gn build: Merge 45ef055d4ff

[ARM][MVE][Intrinsics] Add VMULH/VRMULH intrinsics.
Summary: Add MVE VMULH/VRMULH intrinsics and unit tests.
Reviewers: simon_tatham, ostannard, dmgreen
Subscribers: kristof.beyls, hiraditya, cfe-commits, llvm-commits
Tags: #clang, #llvm
Differential Revision: https://reviews.llvm.org/D70948

[opencl] Fix address space deduction on array variables.
Summary:
- The deduced address space needs applying to its element type as well.
Reviewers: Anastasia
Subscribers: yaxunl, cfe-commits
Tags: #clang
Differential Revision: https://reviews.llvm.org/D70981

[clang-change-namespace] Change file pattern to be an anchored regex

Change Target::FindBreakpointsByName to return Expected<vector>
Summary: Using a BreakpointList corrupts the breakpoints' IDs because 
BreakpointList::Add sets the ID, so use a vector instead, and update the
signature to return the vector wrapped in an llvm::Expected which can
propagate any error from the inner call to StringIsBreakpointName.
Note that, despite the similar name, SBTarget::FindBreakpointsByName 
doesn't suffer the same problem, because it uses a SBBreakpointList, 
which is more like a BreakpointIDList than a BreakpointList under the 
covers.
Add a check to TestBreakpointNames that, without this fix, notices the 
ID getting mutated and fails.
Reviewers: jingham, JDevlieghere
Reviewed By: JDevlieghere
Subscribers: lldb-commits
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D70907

Revert "[llvm][Support] Take in CurrentDirectory as a parameter in
ExpandResponseFiles"
This reverts commit 75656005dbc8866e1888932a68a830b0df403560.

Automaticaly generate copysign-constant-magnitude.ll . NFC

[ELF] Support for PT_GNU_PROPERTY in header and tools
The PT_GNU_PROPERTY is generated by a linker to describe the
.note.gnu.property section. The Linux kernel uses this program header to 
locate the .note.gnu.property section.
It is described in "The Linux gABI extension"
Include support for llvm-readelf, llvm-readobj and the yaml reader and 
writers.
Differential Revision: https://reviews.llvm.org/D70959

Reapply "[llvm][Support] Take in CurrentDirectory as a parameter in
ExpandResponseFiles"
Attemps to fix windows buildbots.

[DebugInfo] Recover debug intrinsics when killing duplicated/empty basic
blocks
When basic blocks are killed, either due to being empty or to being an
if.then or if.else block whose complement contains identical
instructions, some of the debug intrinsics in that block are lost. This
patch sinks those intrinsics into the single successor block, setting
them Undef if necessary to prevent debug info from falling out-of-date.
Differential Revision: https://reviews.llvm.org/D70318

[lldb] Simplify debug_{rnglists,ranges}.s tests
Remove things irrelevant to the test.

[llvm-ar][test] Add to thin archive test coverage
This diff adds test coverage for thin archives including additions to 
existing tests. In some cases I have updated the formats of these tests 
to better match other tests in the archive.
Differential Revision: https://reviews.llvm.org/D70969

Add some missing includes to MicrosoftDemangle.cpp (PR44217)

[libomptarget] Build a minimal deviceRTL for amdgcn
Summary:
[libomptarget] Build a minimal deviceRTL for amdgcn
Repeat of D70414, with an include path fixed. Diff for sanity checking.
The CMakeLists.txt file is functionally identical to the one used in the
aomp fork. Whitespace changes were made based on nvptx/CMakeLists.txt,
plus the copyright notice updated to match (Greg was the original author
so would like his sign off on that here).
This change will build a small subset of the deviceRTL if an appropriate
toolchain is available, e.g. a local install of rocm. Support.h is moved
from nvptx as a dependency of debug.h.
Reviewers: ABataev, jdoerfert
Reviewed By: ABataev
Subscribers: jvesely, mgorny, jfb, openmp-commits, jdoerfert
Tags: #openmp
Differential Revision: https://reviews.llvm.org/D70971

[XCOFF][AIX] Emit TOC entries for object file generation
Summary: Implement emitTCEntry for PPCTargetXCOFFStreamer. Add TC csects
to TOCCsects for object file writing.
Note:
1. I did not include any raw data testing for this object file
generation because TC entries raw data will all be 0 without relocation
implemented. I will add raw data testing as part of relocation testing
later. 2. I removed "Symbol->setFragment(F);" for common symbols because
we
don't need it, and if we have it then we would hit assertions below: 
Assertion `(SymbolContents == SymContentsUnset ||
           SymbolContents == SymContentsOffset) &&
           "Cannot get offset for a common/variable symbol"' failed. 
3.Fixed incorrect TOC-base alignment.
Differential Revision: https://reviews.llvm.org/D70798

[LVI] Restructure caching
Variant on D70103. The caching is switched to always use a BB to cache
entry map, which then contains per-value caches. A separate set contains
value handles with a deletion callback. This allows us to properly
invalidate overdefined values.
A possible alternative would be to always cache by value first and have
per-BB maps/sets in the each cache entry. In that case we could use a
ValueMap and would avoid the separate value handle set. I went with the
BB indexing at the top level to make it easier to integrate D69914, but
possibly that's not the right choice.
Differential Revision: https://reviews.llvm.org/D70376

Small nit in SelectionDAG.h . NFC