platform/upstream/llvm.git
2 years ago[bazel] Port 628fbbef81c5ac806e6dbf2bce18dd44980051b1
Benjamin Kramer [Tue, 26 Jul 2022 13:36:15 +0000 (15:36 +0200)]
[bazel] Port 628fbbef81c5ac806e6dbf2bce18dd44980051b1

2 years ago[DAGCombine] Mask doesn't have to be (EltSize - 1) exactly when combining rotation
wangpc [Tue, 26 Jul 2022 13:11:39 +0000 (21:11 +0800)]
[DAGCombine] Mask doesn't have to be (EltSize - 1) exactly when combining rotation

I think what we need is the least Log2(EltSize) significant bits are known to be ones.

Reviewed By: RKSimon

Differential Revision: https://reviews.llvm.org/D130251

2 years ago[libc] Use nearest_integer instructions to improve expm1f performance.
Tue Ly [Mon, 25 Jul 2022 17:44:46 +0000 (13:44 -0400)]
[libc] Use nearest_integer instructions to improve expm1f performance.

Use nearest_integer instructions to improve expf performance.

Performance tests with CORE-MATH's perf tool:

Before the patch:
```
$ ./perf.sh expm1f
LIBC-location: /home/lnt/experiment/llvm/llvm-project/build/projects/libc/lib/libllvmlibc.a
GNU libc version: 2.31
GNU libc release: stable
CORE-MATH reciprocal throughput   : 10.096
System LIBC reciprocal throughput : 44.036
LIBC reciprocal throughput        : 11.575

$ ./perf.sh expm1f --latency
LIBC-location: /home/lnt/experiment/llvm/llvm-project/build/projects/libc/lib/libllvmlibc.a
GNU libc version: 2.31
GNU libc release: stable
CORE-MATH latency   : 42.239
System LIBC latency : 122.815
LIBC latency        : 50.122
```
After the patch:
```
$ ./perf.sh expm1f
LIBC-location: /home/lnt/experiment/llvm/llvm-project/build/projects/libc/lib/libllvmlibc.a
GNU libc version: 2.31
GNU libc release: stable
CORE-MATH reciprocal throughput   : 10.046
System LIBC reciprocal throughput : 43.899
LIBC reciprocal throughput        : 9.179

$ ./perf.sh expm1f --latency
LIBC-location: /home/lnt/experiment/llvm/llvm-project/build/projects/libc/lib/libllvmlibc.a
GNU libc version: 2.31
GNU libc release: stable
CORE-MATH latency   : 42.078
System LIBC latency : 120.488
LIBC latency        : 41.528
```

Reviewed By: zimmermann6

Differential Revision: https://reviews.llvm.org/D130502

2 years ago[libc] Use nearest_integer instructions to improve expf performance.
Tue Ly [Mon, 25 Jul 2022 16:24:31 +0000 (12:24 -0400)]
[libc] Use nearest_integer instructions to improve expf performance.

Use nearest_integer instructions to improve expf performance.

Performance tests with CORE-MATH's perf tool:

Before the patch:
```
$ ./perf.sh expf
LIBC-location: /home/lnt/experiment/llvm-project/build/projects/libc/lib/libllvmlibc.a
GNU libc version: 2.31
GNU libc release: stable
CORE-MATH reciprocal throughput   : 9.860
System LIBC reciprocal throughput : 7.728
LIBC reciprocal throughput        : 12.363

$ ./perf.sh expf --latency
LIBC-location: /home/lnt/experiment/llvm-project/build/projects/libc/lib/libllvmlibc.a
GNU libc version: 2.31
GNU libc release: stable
CORE-MATH latency   : 42.802
System LIBC latency : 35.941
LIBC latency        : 49.808
```

After the patch:
```
$ ./perf.sh expf
LIBC-location: /home/lnt/experiment/llvm/llvm-project/build/projects/libc/lib/libllvmlibc.a
GNU libc version: 2.31
GNU libc release: stable
CORE-MATH reciprocal throughput   : 9.441
System LIBC reciprocal throughput : 7.382
LIBC reciprocal throughput        : 8.843

$ ./perf.sh expf --latency
LIBC-location: /home/lnt/experiment/llvm/llvm-project/build/projects/libc/lib/libllvmlibc.a
GNU libc version: 2.31
GNU libc release: stable
CORE-MATH latency   : 44.192
System LIBC latency : 37.693
LIBC latency        : 44.145
```

Reviewed By: zimmermann6

Differential Revision: https://reviews.llvm.org/D130498

2 years ago[RISCV] Precommit test for D130251
wangpc [Tue, 26 Jul 2022 13:06:14 +0000 (21:06 +0800)]
[RISCV] Precommit test for D130251

Added tests won't modify the least Log2(EltSize) significant bits.

Reviewed By: RKSimon

Differential Revision: https://reviews.llvm.org/D130252

2 years ago[C++20] [Modules] Don't handle no linkage entities when overloading
Chuanqi Xu [Tue, 26 Jul 2022 13:05:30 +0000 (21:05 +0800)]
[C++20] [Modules] Don't handle no linkage entities when overloading

The original implementation uses `ND->getFormalLinkage() <=
Linkage::InternalLinkage`. It is not right since the spec only says
internal linkage and it doesn't mention 'no linkage'. This matters when
we consider constructors. According to [class.ctor.general]p1,
constructors have no name so constructors have no linkage too.

2 years ago[Debuginfo][llvm-dwarfutil] Add check for unsupported debug sections.
Alexey Lapshin [Mon, 25 Jul 2022 17:08:46 +0000 (20:08 +0300)]
[Debuginfo][llvm-dwarfutil] Add check for unsupported debug sections.

Current DWARFLinker implementation does not support some debug sections
(mainly DWARF v5 sections). This patch adds diagnostic for such sections.
The warning would be displayed for critical(such that could not be removed)
sections and the source file would be skipped. Other unsupported sections
would be removed and warning message should be displayed. The zero exit
status would be returned for both cases.

Reviewed By: JDevlieghere

Differential Revision: https://reviews.llvm.org/D123623

2 years ago[flang] Remove fp128 support for llvm.round and llvm.trunc
Peixin Qiao [Tue, 26 Jul 2022 12:21:51 +0000 (20:21 +0800)]
[flang] Remove fp128 support for llvm.round and llvm.trunc

The fp128 in llvm.round and llvm.trunc is not supported in X86_64 for
now. Revert the support. To support quad precision for llvm.round and
llvm.trunc, it may should be supported using runtime.

Reviewed By: Jean Perier

Differential Revision: https://reviews.llvm.org/D130556

2 years ago[clang][dataflow] Add explicit "AST" nodes for implications and iff
Dmitri Gribenko [Tue, 26 Jul 2022 12:05:53 +0000 (14:05 +0200)]
[clang][dataflow] Add explicit "AST" nodes for implications and iff

Previously we used to desugar implications and biconditionals into
equivalent CNF/DNF as soon as possible. However, this desugaring makes
debug output (Environment::dump()) less readable than it could be.
Therefore, it makes sense to keep the sugared representation of a
boolean formula, and desugar it in the solver.

Reviewed By: sgatev, xazax.hun, wyt

Differential Revision: https://reviews.llvm.org/D130519

2 years ago[NFC] Fix some C++20 warnings
Evgeny Mandrikov [Tue, 26 Jul 2022 12:04:12 +0000 (14:04 +0200)]
[NFC] Fix some C++20 warnings

Without this patch when using CMAKE_CXX_STANDARD=20 Microsoft compiler produces following warnings

clang\include\clang/Basic/DiagnosticIDs.h(48): warning C5054: operator '+': deprecated between enumerations of different types
clang\include\clang/Basic/DiagnosticIDs.h(49): warning C5054: operator '+': deprecated between enumerations of different types
clang\include\clang/Basic/DiagnosticIDs.h(50): warning C5054: operator '+': deprecated between enumerations of different types
clang\include\clang/Basic/DiagnosticIDs.h(51): warning C5054: operator '+': deprecated between enumerations of different types
clang\include\clang/Basic/DiagnosticIDs.h(52): warning C5054: operator '+': deprecated between enumerations of different types
clang\include\clang/Basic/DiagnosticIDs.h(53): warning C5054: operator '+': deprecated between enumerations of different types
clang\include\clang/Basic/DiagnosticIDs.h(54): warning C5054: operator '+': deprecated between enumerations of different types
clang\include\clang/Basic/DiagnosticIDs.h(55): warning C5054: operator '+': deprecated between enumerations of different types
clang\include\clang/Basic/DiagnosticIDs.h(56): warning C5054: operator '+': deprecated between enumerations of different types
clang\include\clang/Basic/DiagnosticIDs.h(57): warning C5054: operator '+': deprecated between enumerations of different types
clang\include\clang/Basic/DiagnosticIDs.h(58): warning C5054: operator '+': deprecated between enumerations of different types
clang\include\clang/Basic/DiagnosticIDs.h(59): warning C5054: operator '+': deprecated between enumerations of different types

Patch By: Godin

Reviewed By: aaron.ballman

Differential Revision: https://reviews.llvm.org/D130476

2 years ago[pseudo] Allow opaque nodes to represent terminals
Sam McCall [Tue, 26 Jul 2022 07:03:02 +0000 (09:03 +0200)]
[pseudo] Allow opaque nodes to represent terminals

This allows incomplete code such as `namespace foo {` to be modeled as a
normal sequence with the missing } represented by an empty opaque node.

Differential Revision: https://reviews.llvm.org/D130551

2 years ago[libc++][NFC] Add missing SHA in ABI changelog
Louis Dionne [Tue, 26 Jul 2022 11:44:26 +0000 (07:44 -0400)]
[libc++][NFC] Add missing SHA in ABI changelog

2 years ago[libc++] Generalize the customizeable assertion handler
Louis Dionne [Mon, 25 Jul 2022 17:19:51 +0000 (13:19 -0400)]
[libc++] Generalize the customizeable assertion handler

Instead of taking a fixed set of arguments, use variadics so that
we can pass arbitrary arguments to the handler. This is the first
step towards using the handler to handle other non-assertion-related
failures, like std::unreachable and an exception being thrown in
-fno-exceptions mode, which would improve user experience by including
additional information in crashes (right now, we call abort() without
additional information).

Differential Revision: https://reviews.llvm.org/D130507

2 years ago[libc++] Remove XFAIL for libcpp_deallocate on AIX, which seems to be passing now
Louis Dionne [Tue, 26 Jul 2022 11:41:53 +0000 (07:41 -0400)]
[libc++] Remove XFAIL for libcpp_deallocate on AIX, which seems to be passing now

2 years ago[gn build] Port 7a5cb15ea6fa
Nico Weber [Tue, 26 Jul 2022 11:28:33 +0000 (07:28 -0400)]
[gn build] Port 7a5cb15ea6fa

2 years ago[bazel] Run autoformatter on BUILD.bazel
Dmitri Gribenko [Tue, 26 Jul 2022 11:11:08 +0000 (13:11 +0200)]
[bazel] Run autoformatter on BUILD.bazel

2 years ago[Clang] [P2025] Analyze only potential scopes for NRVO
Roman Rusyaev [Tue, 26 Jul 2022 10:56:04 +0000 (18:56 +0800)]
[Clang] [P2025] Analyze only potential scopes for NRVO

Before the patch we calculated the NRVO candidate looking at the
variable's whole enclosing scope. The research in [P2025] shows that
looking at the variable's potential scope is better and covers more
cases where NRVO would be safe and desirable.

Many thanks to @Izaron for the original implementation.

Reviewed By: ChuanqiXu

Differential Revision: https://reviews.llvm.org/D119792

2 years ago[bazel] Port 7a5cb15ea6facd82756adafae76d60f36a0b60fd
Benjamin Kramer [Tue, 26 Jul 2022 10:53:23 +0000 (12:53 +0200)]
[bazel] Port 7a5cb15ea6facd82756adafae76d60f36a0b60fd

2 years ago[clang] [docs] Update the changes of C++20 Modules in clang15
Chuanqi Xu [Wed, 6 Jul 2022 09:40:23 +0000 (17:40 +0800)]
[clang] [docs] Update the changes of C++20 Modules in clang15

Since clang15 is going to be branched in July 26, and C++ modules still
lack an update on ReleaseNotes. Although it is not complete yet, I think
it would be better to add one since we've done many works for C++20
Modules in clang15.

Differential Revision: https://reviews.llvm.org/D129138

2 years ago[llvm-objdump,ARM] Fix further test failures.
Simon Tatham [Tue, 26 Jul 2022 10:33:45 +0000 (11:33 +0100)]
[llvm-objdump,ARM] Fix further test failures.

Further test-failure fallout from D130358. There were a handful of
uses of llvm-objdump in the CodeGen tests as well, which have taken me
longer to get to because more things had to be built.

2 years ago[analyzer] Improve loads from reinterpret-cast fields
Balazs Benics [Tue, 26 Jul 2022 10:31:21 +0000 (12:31 +0200)]
[analyzer] Improve loads from reinterpret-cast fields

Consider this example:

```lang=C++
struct header {
  unsigned a : 1;
  unsigned b : 1;
};
struct parse_t {
  unsigned bits0 : 1;
  unsigned bits2 : 2; // <-- header
  unsigned bits4 : 4;
};
int parse(parse_t *p) {
  unsigned copy = p->bits2;
  clang_analyzer_dump(copy);
  // expected-warning@-1 {{reg_$1<unsigned int SymRegion{reg_$0<struct Bug_55934::parse_t * p>}.bits2>}}

  header *bits = (header *)&copy;
  clang_analyzer_dump(bits->b); // <--- Was UndefinedVal previously.
  // expected-warning@-1 {{derived_$2{reg_$1<unsigned int SymRegion{reg_$0<struct Bug_55934::parse_t * p>}.bits2>,Element{copy,0 S64b,struct Bug_55934::header}.b}}}
  return bits->b; // no-warning: it's not UndefinedVal
}
```

`bits->b` should have the same content as the second bit of `p->bits2`
(assuming that the bitfields are in spelling order).

---

The `Store` has the correct bindings. The problem is with the load of `bits->b`.
It will eventually reach `RegionStoreManager::getBindingForField()` with
`Element{copy,0 S64b,struct header}.b`, which is a `FieldRegion`.
It did not find any direct bindings, so the `getBindingForFieldOrElementCommon()`
gets called. That won't find any bindings, but it sees that the variable
is on the //stack//, thus it must be an uninitialized local variable;
thus it returns `UndefinedVal`.

Instead of doing this, it should have created a //derived symbol//
representing the slice of the region corresponding to the member.
So, if the value of `copy` is `reg1`, then the value of `bits->b` should
be `derived{reg1, elem{copy,0, header}.b}`.

Actually, the `getBindingForElement()` already does exactly this for
reinterpret-casts, so I decided to hoist that and reuse the logic.

Fixes #55934

Reviewed By: martong

Differential Revision: https://reviews.llvm.org/D128535

2 years ago[C++20] [Modules] Handle linkage properly for specializations when overloading
Chuanqi Xu [Tue, 26 Jul 2022 10:26:35 +0000 (18:26 +0800)]
[C++20] [Modules] Handle linkage properly for specializations when overloading

Currently, the semantics of linkage in clang is slightly
different from the semantics in C++ spec. In C++ spec, only names
have linkage. So that all entities of the same should share
one linkage. But in clang, different entities of the same could
have different linkage.

It would break a use case where the template have external linkage and
its specialization have internal linkage due to its type argument is
internal linkage. The root cause is that the semantics of internal
linkage in clang is a mixed form of internal linkage and TU-local in
C++ spec. It is hard to solve the root problem and I tried to add a
workaround inplace.

2 years ago[RISCV][Clang] Refactor RISCVVEmitter. (NFC)
Zakk Chen [Tue, 26 Jul 2022 10:14:03 +0000 (10:14 +0000)]
[RISCV][Clang] Refactor RISCVVEmitter. (NFC)

Remove MaskedPrototype and add several fields in RVVIntrinsicRecord,
compute Prototype in runtime.

Reviewed By: rogfer01

Differential Revision: https://reviews.llvm.org/D126741

2 years agoFix MSVC "not all control paths return a value" warning. NFC
Simon Pilgrim [Tue, 26 Jul 2022 09:44:00 +0000 (10:44 +0100)]
Fix MSVC "not all control paths return a value" warning. NFC

2 years ago[RISCV][Clang] Refactor and rename rvv intrinsic related stuff. (NFC)
Zakk Chen [Tue, 26 Jul 2022 09:12:32 +0000 (09:12 +0000)]
[RISCV][Clang] Refactor and rename rvv intrinsic related stuff. (NFC)

This changed is based on https://reviews.llvm.org/D111617

Reviewed By: rogfer01

Differential Revision: https://reviews.llvm.org/D126740

2 years ago[analyzer] Fix unused variable warning in release builds. NFC.
Benjamin Kramer [Tue, 26 Jul 2022 09:26:52 +0000 (11:26 +0200)]
[analyzer] Fix unused variable warning in release builds. NFC.

2 years ago[mlir] Fall back to posix_memalign for aligned_alloc on MacOS
Benjamin Kramer [Tue, 26 Jul 2022 09:14:37 +0000 (11:14 +0200)]
[mlir] Fall back to posix_memalign for aligned_alloc on MacOS

aligned_alloc was added in MacOS 10.15, some users want to support older
versions. The runtime functions makes this easy, so just put in a call
to posix_memalign, which provides the same functionality.

2 years ago[CMake] Fix add_subdirectory llvm builds
Sebastian Neubauer [Tue, 26 Jul 2022 08:40:48 +0000 (10:40 +0200)]
[CMake] Fix add_subdirectory llvm builds

Fixes a regression from D117973, that used CMAKE_BINARY_DIR instead of
LLVM_BINARY_DIR in some places.

Differential Revision: https://reviews.llvm.org/D130555

2 years ago[llvm-objdump,ARM] Fix a lot more tests.
Simon Tatham [Tue, 26 Jul 2022 09:08:56 +0000 (10:08 +0100)]
[llvm-objdump,ARM] Fix a lot more tests.

When I changed the output format of llvm-objdump for Arm and AArch64
in D130358, I hadn't realised llvm-objdump was used so much in the
plain MC tests as well as tests of itself and lld. Sorry!

2 years ago[clang][analyzer][NFC] Use value_or instead of ValueOr
David Spickett [Tue, 26 Jul 2022 09:16:06 +0000 (09:16 +0000)]
[clang][analyzer][NFC] Use value_or instead of ValueOr

The latter is deprecated.

2 years ago[lldb][ARM] Use portable printf tokens for 64 bit types
David Spickett [Tue, 26 Jul 2022 09:04:32 +0000 (09:04 +0000)]
[lldb][ARM] Use portable printf tokens for 64 bit types

Fixes some warnings in the 32 bit build.

2 years ago[llvm-objdump] Fix type mismatch in std::min.
Simon Tatham [Tue, 26 Jul 2022 08:43:26 +0000 (09:43 +0100)]
[llvm-objdump] Fix type mismatch in std::min.

I broke the build just now by trying to do std::min between a size_t
and a uint64_t, which of course worked fine on my 64-bit test platform.

2 years ago[lldb][ARM] Add tests for vpush/vpop D registers
David Spickett [Fri, 22 Jul 2022 15:17:28 +0000 (15:17 +0000)]
[lldb][ARM] Add tests for vpush/vpop D registers

Previously we just checked via S regs and were not checking
memory content after pushes.

The vpush test confirms that the fix in https://reviews.llvm.org/D130307
is working.

Memory will only be checked if an "after" state is provided.

Reviewed By: clayborg

Differential Revision: https://reviews.llvm.org/D130468

2 years ago[flang][OpenMP] Lowering support for default clause
Nimish Mishra [Tue, 26 Jul 2022 08:38:34 +0000 (14:08 +0530)]
[flang][OpenMP] Lowering support for default clause

This patch adds lowering support for default clause.

1. During symbol resolution in semantics, should the enclosing context have
a default data sharing clause defined and a `parser::Name` is not attached
to an explicit data sharing clause, the
`semantics::Symbol::Flag::OmpPrivate` flag (in case of `default(private)`)
and `semantics::Symbol::Flag::OmpFirstprivate` flag (in case of
`default(firstprivate)`) is added to the symbol.

2. During lowering, all symbols having either
   `semantics::Symbol::Flag::OmpPrivate` or
   `semantics::Symbol::Flag::OmpFirstprivate` flag are collected and
   privatised appropriately.

Co-authored-by: Peixin Qiao <qiaopeixin@huawei.com>
Reviewed By: kiranchandramohan

Differential Revision: https://reviews.llvm.org/D123930

2 years agoReassoc FMF should not optimize FMA(a, 0, b) to (b)
Sven van Haastregt [Tue, 26 Jul 2022 08:39:12 +0000 (09:39 +0100)]
Reassoc FMF should not optimize FMA(a, 0, b) to (b)

Optimizing (a * 0 + b) to (b) requires assuming that a is finite and not
NaN. DAGCombiner will do this optimization when the reassoc fast math
flag is set, which is not correct. Change DAGCombiner to only consider
UnsafeMath for this optimization.

Differential Revision: https://reviews.llvm.org/D130232

Co-authored-by: Andrea Faulds <andrea.faulds@arm.com>
2 years ago[llvm-objdump,ARM] Make dumpARMELFData line up with instructions.
Simon Tatham [Tue, 26 Jul 2022 08:20:52 +0000 (09:20 +0100)]
[llvm-objdump,ARM] Make dumpARMELFData line up with instructions.

The whitespace in output lines containing disassembled instructions
was extremely mismatched against that in `.word` lines produced from
dumping literal pools and other data in Arm ELF files. This patch
adjusts `dumpARMELFData` so that it uses the same alignment system as
in the instruction pretty-printers. Now the two classes of line are
aligned sensibly alongside each other.

Reviewed By: DavidSpickett

Differential Revision: https://reviews.llvm.org/D130359

2 years ago[llvm-objdump,ARM] Add PrettyPrinters for Arm and AArch64.
Simon Tatham [Tue, 26 Jul 2022 08:20:46 +0000 (09:20 +0100)]
[llvm-objdump,ARM] Add PrettyPrinters for Arm and AArch64.

Most Arm disassemblers, including GNU objdump and Arm's own `fromelf`,
emit an instruction's raw encoding as a 32-bit words or (for Thumb)
one or two 16-bit halfwords, in logical order rather than according to
their storage endianness. This is generally easier to read: it matches
the encoding diagrams in the architecture spec, it matches the value
you'd write in a `.inst` directive, and it means that fields within
the instruction encoding that span more than one byte (such as branch
offsets or `SVC` immediates) can be read directly in the encoding
without having to mentally reverse the bytes.

llvm-objdump already has a system of PrettyPrinter subclasses which
makes it easy for a target to drop in its own preferred formatting.
This patch adds pretty-printers for all the Arm targets, so that
llvm-objdump will display Arm instruction encodings in their preferred
layout instead of little-endian and bytewise.

Reviewed By: DavidSpickett

Differential Revision: https://reviews.llvm.org/D130358

2 years ago[MC,llvm-objdump,ARM] Target-dependent disassembly resync policy.
Simon Tatham [Tue, 26 Jul 2022 08:20:41 +0000 (09:20 +0100)]
[MC,llvm-objdump,ARM] Target-dependent disassembly resync policy.

Currently, when llvm-objdump is disassembling a code section and
encounters a point where no instruction can be decoded, it uses the
same policy on all targets: consume one byte of the section, emit it
as "<unknown>", and try disassembling from the next byte position.

On an architecture where instructions are always 4 bytes long and
4-byte aligned, this makes no sense at all. If a 4-byte word cannot be
decoded as an instruction, then the next place that a valid
instruction could //possibly// be found is 4 bytes further on.
Disassembling from a misaligned address can't possibly produce
anything that the code generator intended, or that the CPU would even
attempt to execute.

This patch introduces a new MCDisassembler virtual method called
`suggestBytesToSkip`, which allows each target to choose its own
resynchronization policy. For Arm (as opposed to Thumb) and AArch64,
I've filled in the new method to return a fixed width of 4.

Thumb is a more interesting case, because the criterion for
identifying 2-byte and 4-byte instruction encodings is very simple,
and doesn't require the particular instruction to be recognized. So
`suggestBytesToSkip` is also passed an ArrayRef of the bytes in
question, so that it can take that into account. The new test case
shows Thumb disassembly skipping over two unrecognized instructions,
and identifying one as 2-byte and one as 4-byte.

For targets other than Arm and AArch64, this is NFC: the base class
implementation of `suggestBytesToSkip` still returns 1, so that the
existing behavior is unchanged. Other targets can fill in their own
implementations as they see fit; I haven't attempted to choose a new
behavior for each one myself.

I've updated all the call sites of `MCDisassembler::getInstruction` in
llvm-objdump, and also one in sancov, which was the only other place I
spotted the same idiom of `if (Size == 0) Size = 1` after a call to
`getInstruction`.

Reviewed By: DavidSpickett

Differential Revision: https://reviews.llvm.org/D130357

2 years ago[lldb][ARM] Misc improvements to TestEmulations
David Spickett [Mon, 25 Jul 2022 08:48:13 +0000 (08:48 +0000)]
[lldb][ARM] Misc improvements to TestEmulations

* Look for files that end width arm/thumb.dat,
  meaning we don't try to run, for example, vim swap files.
* Print the name of the test that failed.

Reviewed By: clayborg

Differential Revision: https://reviews.llvm.org/D130467

2 years ago[ArgPromotion] Transfer metadata nontemporal to promoted loads
Phoebe Wang [Tue, 26 Jul 2022 08:02:30 +0000 (16:02 +0800)]
[ArgPromotion] Transfer metadata nontemporal to promoted loads

Fixes #56703

Reviewed By: nikic

Differential Revision: https://reviews.llvm.org/D130536

2 years ago[lldb][ARM] Print mismatched registers in emulation tests
David Spickett [Fri, 22 Jul 2022 14:38:03 +0000 (14:38 +0000)]
[lldb][ARM] Print mismatched registers in emulation tests

Also correct the test failed message. It implies that what
it's done is compare the 'before' and 'ater' states from the
test input.

Except that that's the whole point of the test, that the state changes.
It should tell you that it compared the result of the emulation to the
'after'.

Reviewed By: clayborg

Differential Revision: https://reviews.llvm.org/D130464

2 years ago[clang][dataflow] Fix SAT solver crashes on `X ^ X` and `X v X`
Dmitri Gribenko [Tue, 26 Jul 2022 08:16:13 +0000 (10:16 +0200)]
[clang][dataflow] Fix SAT solver crashes on `X ^ X` and `X v X`

BooleanFormula::addClause has an invariant that a clause has no duplicated
literals. When the solver was desugaring a formula into CNF clauses, it
could construct a clause with such duplicated literals in two cases.

Reviewed By: sgatev, ymandel, xazax.hun

Differential Revision: https://reviews.llvm.org/D130522

2 years ago[analyzer] Structured binding to tuple-like types
isuckatcs [Wed, 29 Jun 2022 16:42:07 +0000 (18:42 +0200)]
[analyzer] Structured binding to tuple-like types

Introducing support for creating structured binding
to tuple-like types.

Differential Revision: https://reviews.llvm.org/D128837

2 years ago[LLDB][ARM] Generalise adding register state in emulation tests and add D registers
David Spickett [Fri, 22 Jul 2022 14:13:32 +0000 (14:13 +0000)]
[LLDB][ARM] Generalise adding register state in emulation tests and add D registers

Since some s and d registers overlap we will error if we find both.
This prevents you overwriting one with the other in a test case.

Reviewed By: clayborg

Differential Revision: https://reviews.llvm.org/D130462

2 years ago[AArch64][SVE] Add patterns to select mla/mls
Cullen Rhodes [Tue, 26 Jul 2022 07:52:24 +0000 (07:52 +0000)]
[AArch64][SVE] Add patterns to select mla/mls

Adds patterns for:

  add(a, select(mask, mul(b, c), splat(0))) -> mla(a, mask, b, c)
  sub(a, select(mask, mul(b, c), splat(0))) -> mls(a, mask, b, c)

Reviewed By: paulwalker-arm

Differential Revision: https://reviews.llvm.org/D130492

2 years ago[AArch64][SVE] NFC: Add tests for masked mla/mls patterns (D130492)
Cullen Rhodes [Mon, 25 Jul 2022 12:41:51 +0000 (12:41 +0000)]
[AArch64][SVE] NFC: Add tests for masked mla/mls patterns (D130492)

2 years ago[RISCV] Lazily add RVV C intrinsics.
Kito Cheng [Wed, 13 Jul 2022 07:52:17 +0000 (15:52 +0800)]
[RISCV] Lazily add RVV C intrinsics.

Leverage the method OpenCL uses that adds C intrinsics when the lookup
failed. There is no need to define C intrinsics in the header file any
more. It could help to avoid the large header file to speed up the
compilation of RVV source code. Besides that, only the C intrinsics used
by the users will be added into the declaration table.

This patch is based on https://reviews.llvm.org/D103228 and inspired by
OpenCL implementation.

### Experimental Results

#### TL;DR:

- Binary size of clang increase ~200k, which is +0.07%  for debug build and +0.13% for release build.
- Single file compilation speed up ~33x for debug build and ~8.5x for release build
- Regression time reduce ~10% (`ninja check-all`, enable all targets)

#### Header size change
```
       |      size |     LoC |
------------------------------
Before | 4,434,725 |  69,749 |
After  |     6,140 |     162 |
```

#### Single File Compilation Time
Testcase:
```
#include <riscv_vector.h>

vint32m1_t test_vadd_vv_vfloat32m1_t(vint32m1_t op1, vint32m1_t op2, size_t vl) {
  return vadd(op1, op2, vl);
}
```
##### Debug build:
Before:
```
real    0m19.352s
user    0m19.252s
sys     0m0.092s
```

After:
```
real    0m0.576s
user    0m0.552s
sys     0m0.024s
```

~33x speed up for debug build

##### Release build:
Before:
```
real    0m0.773s
user    0m0.741s
sys     0m0.032s
```

After:
```
real    0m0.092s
user    0m0.080s
sys     0m0.012s
```

~8.5x speed up for release build

#### Regression time
Note: the failed case is `tools/llvm-debuginfod-find/debuginfod.test` which is unrelated to this patch.

##### Debug build
Before:
```
Testing Time: 1358.38s
  Skipped          :    11
  Unsupported      :   446
  Passed           : 75767
  Expectedly Failed:   190
  Failed           :     1
```
After
```
Testing Time: 1220.29s
  Skipped          :    11
  Unsupported      :   446
  Passed           : 75767
  Expectedly Failed:   190
  Failed           :     1
```
##### Release build
Before:
```
Testing Time: 381.98s
  Skipped          :    12
  Unsupported      :  1407
  Passed           : 74765
  Expectedly Failed:   176
  Failed           :     1
```
After:
```
Testing Time: 346.25s
  Skipped          :    12
  Unsupported      :  1407
  Passed           : 74765
  Expectedly Failed:   176
  Failed           :     1
```

#### Binary size of clang

##### Debug build
Before
```
   text    data     bss     dec     hex filename
335261851       12726004         552812 348540667       14c64efb        bin/clang
```
After
```
   text    data     bss     dec     hex filename
335442803       12798708         552940 348794451       14ca2e53        bin/clang
```
+253K, +0.07% code size

##### Release build
Before
```
   text    data     bss     dec     hex filename
144123975       8374648  483140 152981763       91e5103 bin/clang
```
After
```
   text    data     bss     dec     hex filename
144255762       8447296  483268 153186326       9217016 bin/clang
```
+204K, +0.13%

Authored-by: Kito Cheng <kito.cheng@sifive.com>
Co-Authored-by: Hsiangkai Wang <kai.wang@sifive.com>
Reviewed By: khchen, aaron.ballman

Differential Revision: https://reviews.llvm.org/D111617

2 years ago[lldb][AArch64] Add support for memory tags in core files
David Spickett [Mon, 11 Jul 2022 12:26:55 +0000 (13:26 +0100)]
[lldb][AArch64] Add support for memory tags in core files

This teaches ProcessElfCore to recognise the MTE tag segments.

https://www.kernel.org/doc/html/latest/arm64/memory-tagging-extension.html#core-dump-support

These segments contain all the tags for a matching memory segment
which will have the same size in virtual address terms. In real terms
it's 2 tags per byte so the data in the segment is much smaller.

Since MTE is the only tag type supported I have hardcoded some
things to those values. We could and should support more formats
as they appear but doing so now would leave code untested until that
happens.

A few things to note:
* /proc/pid/smaps is not in the core file, only the details you have
  in "maps". Meaning we mark a region tagged only if it has a tag segment.
* A core file supports memory tagging if it has at least 1 memory
  tag segment, there is no other flag we can check to tell if memory
  tagging was enabled. (unlike a live process that can support memory
  tagging even if there are currently no tagged memory regions)

Tests have been added at the commands level for a core file with
mte and without.

There is a lot of overlap between the "memory tag read" tests here and the unit tests for
MemoryTagManagerAArch64MTE::UnpackTagsFromCoreFileSegment, but I think it's
worth keeping to check ProcessElfCore doesn't cause an assert.

Depends on D129487

Reviewed By: omjavaid

Differential Revision: https://reviews.llvm.org/D129489

2 years ago[Libomptarget] Add checks for AMDGPU TargetID using new image info
Saiyedul Islam [Mon, 25 Jul 2022 16:40:06 +0000 (11:40 -0500)]
[Libomptarget] Add checks for AMDGPU TargetID using new image info

This patch extends the is_valid_binary routine to also check if the
binary's target ID matches the one parsed from the system's runtime
environment.
This should allow us to only use the binary whose compute capability
matches, allowing us to support basic multi-architecture binaries for
AMDGPU.
It also handles compatibility testing of target IDs of the image and
the enviornment.

Depends on D127432

Reviewed By: JonChesterfield

Differential Revision: https://reviews.llvm.org/D127769

2 years ago[analyzer] Lambda capture non-POD type array
isuckatcs [Sun, 17 Jul 2022 17:04:45 +0000 (19:04 +0200)]
[analyzer] Lambda capture non-POD type array

This patch introduces a new `ConstructionContext` for
lambda capture. This `ConstructionContext` allows the
analyzer to construct the captured object directly into
it's final region, and makes it possible to capture
non-POD arrays.

Differential Revision: https://reviews.llvm.org/D129967

2 years ago[cmake] Fix missing paren in `FindPrefixFromConfig`
John Ericson [Tue, 26 Jul 2022 07:29:11 +0000 (07:29 +0000)]
[cmake] Fix missing paren in `FindPrefixFromConfig`

This was in CMake syntax generation, so we didn't catch it eval time.

Follow up from D117973

2 years ago[flang] Rename variables in test. NFCI
Diana Picus [Thu, 30 Jun 2022 12:41:24 +0000 (12:41 +0000)]
[flang] Rename variables in test. NFCI

Use pertinent names instead of numbered values, to make it easier to
update the test in future patches.

Differential Revision: https://reviews.llvm.org/D130474

2 years ago[ARM] Add Tag_CPU_arch missing value descriptions in attribute parser
Victor Campos [Tue, 12 Jul 2022 15:13:12 +0000 (16:13 +0100)]
[ARM] Add Tag_CPU_arch missing value descriptions in attribute parser

The ARM attribute parser for Tag_CPU_arch is missing value descriptions
for Armv8-A and Armv8-R.

This patch adds these descriptions.

Reviewed By: pratlucas

Differential Revision: https://reviews.llvm.org/D129631

2 years ago[LLDB][Reliability] Fix register value unpacking
Slava Gurevich [Thu, 21 Jul 2022 20:20:10 +0000 (13:20 -0700)]
[LLDB][Reliability] Fix register value unpacking

Fix incorrect direction for bit-shifting.

Coverity warning 1355603 (scan.coverity.com)

Differential Revision: https://reviews.llvm.org/D130307

2 years ago[BOLT] Support files with no symbols
Amir Ayupov [Tue, 26 Jul 2022 07:07:34 +0000 (00:07 -0700)]
[BOLT] Support files with no symbols

`LastSymbol` handling in `discoverFileObjects` assumes a non-zero number of
symbols in an object file. It's not the case for broken_dynsym.test added in
D130073, and potentially other stripped binaries.

Reviewed By: maksfb

Differential Revision: https://reviews.llvm.org/D130544

2 years ago[analyzer] ArrayInitLoopExpr with array of non-POD type
isuckatcs [Sun, 17 Jul 2022 16:25:16 +0000 (18:25 +0200)]
[analyzer] ArrayInitLoopExpr with array of non-POD type

This patch introduces the evaluation of ArrayInitLoopExpr
in case of structured bindings and implicit copy/move
constructor. The idea is to call the copy constructor for
every element in the array. The parameter of the copy
constructor is also manually selected, as it is not a part
of the CFG.

Differential Revision: https://reviews.llvm.org/D129496

2 years ago[LoongArch] Use `end namespace xxx` style comment. NFC
Weining Lu [Tue, 26 Jul 2022 06:55:25 +0000 (14:55 +0800)]
[LoongArch] Use `end namespace xxx` style comment. NFC

2 years ago[clang-format] Fix a hang when formatting C# $@ string literals
owenca [Sat, 23 Jul 2022 06:39:43 +0000 (23:39 -0700)]
[clang-format] Fix a hang when formatting C# $@ string literals

Fixes #56624.

Differential Revision: https://reviews.llvm.org/D130411

2 years ago[CMake][Fuchsia] Enable assertions and backtraces in stage 1 build
Alex Brachet [Tue, 26 Jul 2022 06:08:52 +0000 (06:08 +0000)]
[CMake][Fuchsia] Enable assertions and backtraces in stage 1 build

Differential Revision: https://reviews.llvm.org/D130514

2 years ago[ADT] Deprecate Optional::getValueOr (NFC)
Kazu Hirata [Tue, 26 Jul 2022 06:01:02 +0000 (23:01 -0700)]
[ADT] Deprecate Optional::getValueOr (NFC)

This patch deprecates getValueOr in favor of value_or.

Differential Revision: https://reviews.llvm.org/D130140

2 years ago[flang] Use value or * instead of getValue (NFC)
Kazu Hirata [Tue, 26 Jul 2022 06:01:01 +0000 (23:01 -0700)]
[flang] Use value or * instead of getValue (NFC)

This patch replaces x.getValue() with *x if the reference is obviously
protected by a presence check.  Otherwise, it replaces x.getValue()
with x.value().

2 years agoRemove redundaunt virtual specifiers (NFC)
Kazu Hirata [Tue, 26 Jul 2022 06:00:59 +0000 (23:00 -0700)]
Remove redundaunt virtual specifiers (NFC)

Identified with tidy-modernize-use-override.

2 years agoUse isa instead of dyn_cast (NFC)
Kazu Hirata [Tue, 26 Jul 2022 06:00:58 +0000 (23:00 -0700)]
Use isa instead of dyn_cast (NFC)

2 years ago[mlir] Use value_or (NFC)
Kazu Hirata [Tue, 26 Jul 2022 06:00:56 +0000 (23:00 -0700)]
[mlir] Use value_or (NFC)

2 years agofix comment typo to cycle bots
Nico Weber [Tue, 26 Jul 2022 05:55:10 +0000 (01:55 -0400)]
fix comment typo to cycle bots

2 years ago[gn build] tweak how symbol_exports map files look on linux, for 94c00c10e
Nico Weber [Tue, 26 Jul 2022 05:50:48 +0000 (01:50 -0400)]
[gn build] tweak how symbol_exports map files look on linux, for 94c00c10e

After bc39d7bdd497 (ported to GN in 94c00c10e), libclang uses symbol_exports,
and clang/test/LibClang/symbols.test wants the versioned name to be `LLVM_[0-9]$`
instead of `FOO`.

2 years ago[CodeMetrics] use hasOneLiveUse instead of hasOneUse while analyzing inlinable callsites
Sinan Lin [Tue, 26 Jul 2022 05:45:13 +0000 (13:45 +0800)]
[CodeMetrics] use hasOneLiveUse instead of hasOneUse while analyzing inlinable callsites

It would be better for CodeMetrics to use hasOneLiveUse while analyzing
static and called once callsites, since inline cost now uses
hasOneLiveUse instead of hasOneUse to avoid overpessimization on dead
constant cases (since this patch https://reviews.llvm.org/D109294).

This change has no noticeable influence now, but it helps improve the
accuracy of cost models of passes that use CodeMetrics.

Reviewed By: fhahn, nikic

Differential Revision: https://reviews.llvm.org/D130461

2 years ago[gn build] port bc39d7bdd497 (libclang.map -> libclang.exports)
Nico Weber [Tue, 26 Jul 2022 05:39:15 +0000 (01:39 -0400)]
[gn build] port bc39d7bdd497 (libclang.map -> libclang.exports)

2 years ago[LoopDataPrefetch] Fix crash when TTI doesn't set CacheLineSize
zhongyunde [Tue, 26 Jul 2022 05:05:52 +0000 (13:05 +0800)]
[LoopDataPrefetch] Fix crash when TTI doesn't set CacheLineSize

Fix https://github.com/llvm/llvm-project/issues/56681

Reviewed By: RKSimon

Differential Revision: https://reviews.llvm.org/D130418

2 years agolibclang.so: Make SONAME the same as LLVM version
Tom Stellard [Tue, 26 Jul 2022 05:02:47 +0000 (22:02 -0700)]
libclang.so: Make SONAME the same as LLVM version

This partially reverts c7b3a91017d26266d7556b1ac7c49b06f0109b91.  Having
libclang.so with a different SONAME than the other LLVM libraries was
causing a lot of confusion for users.  Also, this change did not really
acheive it's purpose of allowing apps to use newer versions of
libclang.so without rebuilding, because a new version of libclang.so
requires a new version of libLLVM.so, which does not have a stable ABI.

Reviewed By: MaskRay

Differential Revision: https://reviews.llvm.org/D129160

2 years ago[BOLT][TEST] Update fptr.test
Amir Ayupov [Tue, 26 Jul 2022 05:00:24 +0000 (22:00 -0700)]
[BOLT][TEST] Update fptr.test

The test exercises an implicit ptr-to-int conversion which is made an error in
D129881. We acknowledge the error but still want to test this case.
Add `-Wno-int-conversion` to silence the error.

Reviewed By: maksfb

Differential Revision: https://reviews.llvm.org/D130546

2 years ago[DirectX backend] [NFC]Add DXILOpBuilder to generate DXIL operation
Xiang Li [Sat, 2 Jul 2022 20:44:46 +0000 (13:44 -0700)]
[DirectX backend] [NFC]Add DXILOpBuilder to generate DXIL operation

A new helper class DXILOpBuilder is added to create DXIL op function calls.

TableGen backend for DXILOperation will create table for DXIL op function parameter types.
When create DXIL op function, these parameter types will used to create the function type.

Reviewed By: bogner

Differential Revision: https://reviews.llvm.org/D130291

2 years ago[CodeGen] Consider MangleCtx when move lazy emission States
Jun Zhang [Sat, 23 Jul 2022 05:55:10 +0000 (13:55 +0800)]
[CodeGen] Consider MangleCtx when move lazy emission States

Also move MangleCtx when moving some lazy emission states in
CodeGenModule. Without this patch clang-repl hits an invalid address
access when passing `-Xcc -O2` flag.

Signed-off-by: Jun Zhang <jun@junz.org>
Differential Revision: https://reviews.llvm.org/D130420

2 years ago[JITLink][COFF] Don't dead strip seh frame of exported function.
Sunho Kim [Tue, 26 Jul 2022 04:04:12 +0000 (13:04 +0900)]
[JITLink][COFF] Don't dead strip seh frame of exported function.

Adds keep-alive edges to pdata section to prevent dead strip of block when its parent function is alive.

Reviewed By: lhames

Differential Revision: https://reviews.llvm.org/D129945

2 years ago[JITLink][COFF] Consider lib/dll files in llvm-jitlink.
Sunho Kim [Tue, 26 Jul 2022 03:59:44 +0000 (12:59 +0900)]
[JITLink][COFF] Consider lib/dll files in llvm-jitlink.

Consider lib/dll files in llvm-jitlink.

Reviewed By: lhames

Differential Revision: https://reviews.llvm.org/D129944

2 years ago[X86][DAGISel] Don't widen shuffle element with AVX512
Luo, Yuanke [Tue, 12 Jul 2022 03:00:08 +0000 (11:00 +0800)]
[X86][DAGISel] Don't widen shuffle element with AVX512

Currently the X86 shuffle lowering would widen the element type for
shuffle if the mask element value is adjacent. For below example

  %t2 = add nsw <16 x i32> %t0, %t1
  %t3 = sub nsw <16 x i32> %t0, %t1
  %t4 = shufflevector <16 x i32> %t2, <16 x i32> %t3,
                      <16 x i32> <i32 16, i32 17, i32 2, i32 3, i32 4,
                       i32 5, i32 6, i32 7, i32 8, i32 9, i32 10,
                       i32 11, i32 12, i32 13, i32 14, i32 15>

  ret <16 x i32> %t4

Compiler would transform the shuffle to
  %t4 = shufflevector <8 x i64> %t2, <8 x i64> %t3,
                      <8 x i64> <i32 8, i32 1, i32 2, i32 3, i32 4,
                                 i32 5, i32 6, i32 7>
This may lose the oppotunity to let ISel select mask instruction when
avx512 is enabled.

This patch is to prevent the tranform when avx512 feature is enabled.
Thank Simon for the idea.

Differential Revision: https://reviews.llvm.org/D129537

2 years ago[LLDB][NFC][Reliability] Fix uninitialized variables from Coverity scan. Part 2
Slava Gurevich [Mon, 25 Jul 2022 22:52:21 +0000 (15:52 -0700)]
[LLDB][NFC][Reliability] Fix uninitialized variables from Coverity scan. Part 2

Improve LLDB reliability by fixing the following "uninitialized variables" static code inspection warnings from
scan.coverity.com:

1476275, 1274012, 1455035, 1364789, 1454282
1467483, 1406152, 1406255, 1454837, 1454416
1467446, 1462022, 1461909, 1420566, 1327228
1367767, 1431254, 1467299, 1312678, 1431780
1454731, 1490403

Differential Revision: https://reviews.llvm.org/D130528

2 years ago[flang] Remove unused variable lastPrivBlock (NFC)
Kazu Hirata [Tue, 26 Jul 2022 03:52:22 +0000 (20:52 -0700)]
[flang] Remove unused variable lastPrivBlock (NFC)

This fixes the warning:

  llvm-project/flang/lib/Lower/OpenMP.cpp:94:10: error: unused
  variable 'lastPrivBlock' [-Werror,-Wunused-variable]

2 years ago[JITLink][COFF] Implement IMAGE_COMDAT_SELECT_LARGEST partially.
Sunho Kim [Tue, 26 Jul 2022 03:51:33 +0000 (12:51 +0900)]
[JITLink][COFF] Implement IMAGE_COMDAT_SELECT_LARGEST partially.

Implement IMAGE_COMDAT_SELECT_LARGEST partially. It's going to fail if larger symbol appears but this hasn't happened at least in vcruntime library.

We probably would not implement this properly as it requires complicated runtime patching which is not of nature of JIT. However, we'd like to validate if larger section appears and report to the user in the near future.

Reviewed By: lhames

Differential Revision: https://reviews.llvm.org/D129941

2 years ago[JITLink][COFF] Implement IMAGE_WEAK_EXTERN_SEARCH_NOLIBRARY/LIBRARY.
Sunho Kim [Tue, 26 Jul 2022 03:46:34 +0000 (12:46 +0900)]
[JITLink][COFF] Implement IMAGE_WEAK_EXTERN_SEARCH_NOLIBRARY/LIBRARY.

Implement IMAGE_WEAK_EXTERN_SEARCH_NOLIBRARY/LIBRARY characteristics flag.

Since COFFObjectFile class will set undefined flag for symbols with no alias flag, ORC ObjectFileInterface will not pull in this symbol. So, we only need to make sure the scope is local. NOLIBRARY and LIBRARY are handled in the same way for now. (which is what lld does right now)

Reviewed By: lhames

Differential Revision: https://reviews.llvm.org/D129939

2 years ago[JITLink][COFF] Handle duplicate external symbols.
Sunho Kim [Tue, 26 Jul 2022 03:44:04 +0000 (12:44 +0900)]
[JITLink][COFF] Handle duplicate external symbols.

Handles duplicate external symbols. This happens in few static libraries generaed from msvc toolchain.

Reviewed By: lhames

Differential Revision: https://reviews.llvm.org/D129937

2 years ago[bazel] Add new rule for c60b897d22b2feab3282c4fc2b390bc87560c7de
Weverything [Tue, 26 Jul 2022 03:26:19 +0000 (20:26 -0700)]
[bazel] Add new rule for c60b897d22b2feab3282c4fc2b390bc87560c7de

2 years ago[llvm][cmake] Make `install_symlink` workflow work with absolute install dirs
John Ericson [Mon, 25 Jul 2022 21:17:34 +0000 (21:17 +0000)]
[llvm][cmake] Make `install_symlink` workflow work with absolute install dirs

If `CMAKE_INSTALL_BINDIR` is a different absolute path per project, as
it is with NixOS when we install every package to its own prefix, the
old way fails when the absolute path gets prepended with `CMAKE_INSTALL_PREFIX`.

The `extend_path` function does what we want, but it is currently internal-only. So easier to just inline the one small case of it we need.

Also fix one stray `bin` -> `CMAKE_INSTALL_BINDIR`

Reviewed By: sebastian-ne

Differential Revision: https://reviews.llvm.org/D101070

2 years ago[DAGCombiner] Teach scalarizeExtractedBinop to support scalable splat.
jacquesguan [Thu, 14 Jul 2022 02:41:42 +0000 (10:41 +0800)]
[DAGCombiner] Teach scalarizeExtractedBinop to support scalable splat.

This patch supports the scalable splat part for scalarizeExtractedBinop.

Differential Revision: https://reviews.llvm.org/D129725

2 years agoRevert "[LLDB][NFC][Reliability] Fix uninitialized variables from Coverity scan....
Slava Gurevich [Tue, 26 Jul 2022 01:23:19 +0000 (18:23 -0700)]
Revert "[LLDB][NFC][Reliability] Fix uninitialized variables from Coverity scan. Part 2"

This reverts commit b9aedd94e6796e4b4866ab4c091b736b3db58cb7.

2 years ago[mlir][Math] Add constant folder for Exp2Op.
jacquesguan [Mon, 25 Jul 2022 10:11:53 +0000 (18:11 +0800)]
[mlir][Math] Add constant folder for Exp2Op.

This patch adds constant folder for Exp2Op which only supports single and double precision floating-point.

Differential Revision: https://reviews.llvm.org/D130472

2 years ago[mlir] SCCP add missing pessimistic setting
Jacques Pienaar [Tue, 26 Jul 2022 00:41:17 +0000 (17:41 -0700)]
[mlir] SCCP add missing pessimistic setting

When this was updated in D127139 the update in-place case was no longer
marked as pessimistic. Add back in.

Differential Revision: https://reviews.llvm.org/D130453

2 years ago[mlir][Parser] Fix memory leak when failing to parse a forward declared block
River Riddle [Tue, 19 Jul 2022 23:12:02 +0000 (16:12 -0700)]
[mlir][Parser] Fix memory leak when failing to parse a forward declared block

This commit fixes a failure edge case where we accidentally drop forward
declared blocks in the error case. This allows for running the
invalid.mlir test in asan mode now.

Fixes #51387

Differential Revision: https://reviews.llvm.org/D130132

2 years ago[Flang][OpenMP] Add support for lastprivate clause for worksharing loop.
Arnamoy Bhattacharyya [Tue, 26 Jul 2022 00:31:23 +0000 (20:31 -0400)]
[Flang][OpenMP] Add support for lastprivate clause for worksharing loop.

This patch adds an initial support to the lastprivate clause for worksharing loop.  The patch creates necessary control flow to guarantee the store of the value from the logical last iteration of the workshare loop.

Reviewed By: kiranchandramohan

Differential Revision: https://reviews.llvm.org/D130027

2 years ago[lld-macho] Implement -hidden-l
Daniel Bertalan [Mon, 25 Jul 2022 22:51:28 +0000 (00:51 +0200)]
[lld-macho] Implement -hidden-l

Similarly to -load_hidden, this flag instructs the linker to not export
symbols from the specified archive. While that flag takes a path,
-hidden-l looks for the specified library name in the search path.

The test changes are needed because -hidden-lfoo resolves to libfoo.a,
not foo.a.

Differential Revision: https://reviews.llvm.org/D130529

2 years ago[LLDB][NFC][Reliability] Fix uninitialized variables from Coverity scan. Part 2
Slava Gurevich [Mon, 25 Jul 2022 22:52:21 +0000 (15:52 -0700)]
[LLDB][NFC][Reliability] Fix uninitialized variables from Coverity scan. Part 2

Improve LLDB reliability by fixing the following "uninitialized variables" static code inspection warnings from
scan.coverity.com:

1476275, 1274012, 1455035, 1364789, 1454282
1467483, 1406152, 1406255, 1454837, 1454416
1467446, 1462022, 1461909, 1420566, 1327228
1367767, 1431254, 1467299, 1312678, 1431780
1454731, 1490403

Differential Revision: https://reviews.llvm.org/D130528

2 years ago[mlir] Refactor the Parser library in preparation for an MLIR binary format
River Riddle [Sun, 10 Jul 2022 08:00:21 +0000 (01:00 -0700)]
[mlir] Refactor the Parser library in preparation for an MLIR binary format

The current Parser library is solely focused on providing API for
the textual MLIR format, but MLIR will soon also provide a binary
format. This commit renames the current Parser library to AsmParser to
better correspond to what the library is actually intended for. A new
Parser library is added which will act as a unified parser interface
between both text and binary formats. Most parser clients are
unaffected, given that the unified interface is essentially the same as
the current interface. Only clients that rely on utilizing the
AsmParserState, or those that want to parse Attributes/Types need to be
updated to point to the AsmParser library.

Differential Revision: https://reviews.llvm.org/D129605

2 years ago[GlobalISel] Fix miscompile of G_UREM + G_UDIV due to not checking for equality
Amara Emerson [Mon, 25 Jul 2022 22:13:49 +0000 (15:13 -0700)]
[GlobalISel] Fix miscompile of G_UREM + G_UDIV due to not checking for equality
of the first operands of each.

Fixes issue #55287

Differential Revision: https://reviews.llvm.org/D130525

2 years ago[Clang] Fix how we set the NumPositiveBits on an EnumDecl to cover the case of single...
Shafik Yaghmour [Mon, 25 Jul 2022 22:56:44 +0000 (15:56 -0700)]
[Clang] Fix how we set the NumPositiveBits on an EnumDecl to cover the case of single enumerator with value zero or an empty enum

Currently in Sema::ActOnEnumBody(...) when calculating NumPositiveBits we miss
the case where there is only a single enumerator with value zero and the case of
an empty enum. In both cases we end up with zero positive bits when in fact we
need one bit to store the value zero.

This PR updates the calculation to account for these cases.

Differential Revision: https://reviews.llvm.org/D130301

2 years ago[RISCV] Refactor translateSetCCForBranch to prepare for D130508. NFC.
Craig Topper [Mon, 25 Jul 2022 22:42:42 +0000 (15:42 -0700)]
[RISCV] Refactor translateSetCCForBranch to prepare for D130508. NFC.

D130508 handles more constants than just 1 or -1. We need to extract
the constant instead of relying isOneConstant or isAllOnesConstant.

2 years ago[IRBuilder] Add assert for AtomicRMW ordering
Alexander Shaposhnikov [Mon, 25 Jul 2022 22:51:25 +0000 (22:51 +0000)]
[IRBuilder] Add assert for AtomicRMW ordering

Add assert for AtomicRMW: Ordering != AtomicOrdering::Unordered
(https://github.com/llvm/llvm-project/blob/main/llvm/lib/IR/Verifier.cpp#L3944)
and adjust expandAtomicStore accordingly.

Test plan:
1/ ninja check-llvm check-clang check-lld
2/ Bootstrapped LLVM/Clang pass tests

Differential revision: https://reviews.llvm.org/D130457

2 years ago[BOLT] Process each block only once in fixCFGForPIC
Fabian Parzefall [Mon, 25 Jul 2022 21:48:48 +0000 (14:48 -0700)]
[BOLT] Process each block only once in fixCFGForPIC

Rather than iterating over the whole function from the start until no
internal calls are found, process each block only once and continue
processing after splitting. This version of the function also does not
seemingly invalidate iterators from within the loop.

Reviewed By: maksfb

Differential Revision: https://reviews.llvm.org/D130436

2 years ago[Driver] Ignore unimplemented -mtune= for ARM/PowerPC
Fangrui Song [Mon, 25 Jul 2022 22:05:38 +0000 (15:05 -0700)]
[Driver] Ignore unimplemented -mtune= for ARM/PowerPC

This compensates for 8f0c901c1a172313a32bc06a1fcface76cd1220f which enabled
-Wunused-command-line-argument for unimplemented -mtune= in the generic code.
Ignoring -mtune= appears to be longstanding and the error-free behavior in the
presence of -Werror is unfortunately relied on by the Linux kernel's arm and
powerpc ports. Ignore the warnings for the upcoming 15.0.0 branch and will
implement functionality to fill the test gap soon.

Link: https://github.com/ClangBuiltLinux/linux/issues/1674
2 years ago[mlir][NFC] Remove TypeRange's constructors that cause ambiguity
lipracer [Mon, 25 Jul 2022 21:33:51 +0000 (15:33 -0600)]
[mlir][NFC] Remove TypeRange's constructors that cause ambiguity

ArrayRef<Value> can implicit convert to ValueRange,when we call TypeRange(SmallVector<Value>) is ambiguity.
TypeRange(ValueRange values)
TypeRange(ArrayRef<Value> values)

Reviewed By: rriddle, Mogball

Differential Revision: https://reviews.llvm.org/D129475

2 years agoSplit class ValueRange to a new file
lipracer [Mon, 25 Jul 2022 20:42:18 +0000 (14:42 -0600)]
Split class ValueRange to a new file

When we apply parent patch : https://reviews.llvm.org/D129475
The prompt I get with the clang compiler is: ValueRange is imcomplete type,ValueRange is a forward declaration in the file TypeRange.h, and the file OperationSupport.h already includes the file TypeRange.h.The class TypeRange and the class ValueRange depend on each other.

Reviewed By: rriddle, Mogball

Differential Revision: https://reviews.llvm.org/D130332