| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
| |
llvm-svn: 298770
|
| |
|
|
|
|
| |
well.
llvm-svn: 298769
|
| |
|
|
| |
llvm-svn: 298768
|
| |
|
|
|
|
|
|
| |
For target environment amdgiz and amdgizcl (giz means Generic Is Zero), AMDGPU will use new address space mapping where generic address space is 0 and private address space is 5. The data layout is also changed correspondingly.
Differential Revision: https://reviews.llvm.org/D31210
llvm-svn: 298767
|
| |
|
|
|
|
| |
Remove a stray letter, add a missing letter. No functional change.
llvm-svn: 298766
|
| |
|
|
|
|
|
|
| |
This typically is only for a new enough linker (bfd >= 2.16.2 or gold), but
our ppc suppport post-dates this and it should work on all linux platforms. It
is guaranteed to work on all elfv2 platforms.
llvm-svn: 298765
|
| |
|
|
|
|
| |
"to due" -> "due to". No functional change.
llvm-svn: 298764
|
| |
|
|
|
|
|
| |
Fix a stray capital letter in the middle of a sentence. No functional
change.
llvm-svn: 298763
|
| |
|
|
|
|
| |
Make it consistent with the rest of LLVM.
llvm-svn: 298762
|
| |
|
|
|
|
| |
than the default of 8 in clang, fix and update tests accordingly.
llvm-svn: 298761
|
| |
|
|
|
|
|
| |
This avoids 'used but not defined' warnings in Release builds
with GCC.
llvm-svn: 298760
|
| |
|
|
|
|
|
| |
The le triple didn't exist until power8, so use that as a default (this
also matches what gcc does).
llvm-svn: 298759
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Switch data layout by target triple environment amdgiz and amdgizcl indicating using of an address space mapping in which generic address space is 0.
amdgiz is for non-OpenCL environment where generic address space is 0.
amdgizcl is for OpenCL environment where generic address space is 0.
Differential Revision: https://reviews.llvm.org/D31211
llvm-svn: 298758
|
| |
|
|
| |
llvm-svn: 298757
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When possible, put ASan ctor/dtor in comdat.
The only reason not to is global registration, which can be
TU-specific. This is not the case when there are no instrumented
globals. This is also limited to ELF targets, because MachO does
not have comdat, and COFF linkers may GC comdat constructors.
The benefit of this is a lot less __asan_init() calls: one per DSO
instead of one per TU. It's also necessary for the upcoming
gc-sections-for-globals change on Linux, where multiple references to
section start symbols trigger quadratic behaviour in gold linker.
llvm-svn: 298756
|
| |
|
|
|
|
| |
minimization if another bug was found during minimization (https://github.com/google/oss-fuzz/issues/452)
llvm-svn: 298755
|
| |
|
|
| |
llvm-svn: 298754
|
| |
|
|
|
|
|
|
| |
Only depend on LLD if it is going to be built.
Re-land of r298174 which got reverted in r298287.
llvm-svn: 298753
|
| |
|
|
| |
llvm-svn: 298752
|
| |
|
|
| |
llvm-svn: 298751
|
| |
|
|
|
|
|
|
|
|
| |
If we have an array of a user-defined aggregates for which there was an
ODR violation, then the array size will not necessarily match the number
of elements times the size of the element.
Fixes PR32383
llvm-svn: 298750
|
| |
|
|
|
|
| |
I just didn't know that raw_fd_ostream has has_colors() function.
llvm-svn: 298749
|
| |
|
|
| |
llvm-svn: 298748
|
| |
|
|
|
|
|
| |
When I tested r298734, I thought that red zones were enabled by default like in
X86. Since red zones are behind a flag on AArch64 the testing wasn't true.
llvm-svn: 298747
|
| |
|
|
| |
llvm-svn: 298746
|
| |
|
|
|
|
|
|
| |
Add/Sub in SimplifyDemandedUseBits without recursing into ComputeKnownBits"
Tsan bot is failing.
llvm-svn: 298745
|
| |
|
|
| |
llvm-svn: 298744
|
| |
|
|
|
|
|
|
| |
Asserting the result of strtok when we expect delimiter overflow is
flaky, the result depends on the random state of memory right after the
delimiters.
llvm-svn: 298743
|
| |
|
|
| |
llvm-svn: 298742
|
| |
|
|
| |
llvm-svn: 298741
|
| |
|
|
|
|
| |
crash minimization (https://github.com/google/oss-fuzz/issues/250)
llvm-svn: 298740
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This is another step towards implementing register classes with
parametrized register/spill sizes and value types.
This is an updated version of r298652. The difference is that MCRegister-
Class still contains register size, available as getPhysRegSize(). The
old function getSize was retained as a temporary measure to avoid build
breakage for out-of-tree targets.
llvm-svn: 298739
|
| |
|
|
|
|
| |
tsan_libdispatch_mac.cc.
llvm-svn: 298738
|
| |
|
|
|
|
|
|
| |
If the branch condition for a loop was a phi which itself
was fed from a phi from a loop, it isn't safe to try
to delete the phi until after the loop is handled.
llvm-svn: 298737
|
| |
|
|
| |
llvm-svn: 298736
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reason: breaks linking Chromium with LLD + ThinLTO (a pass crashes)
LLVM bug: https://bugs.llvm.org//show_bug.cgi?id=32413
Original change description:
[LV] Vectorize GEPs
This patch adds support for vectorizing GEPs. Previously, we only generated
vector GEPs on-demand when creating gather or scatter operations. All GEPs from
the original loop were scalarized by default, and if a pointer was to be stored
to memory, we would have to build up the pointer vector with insertelement
instructions.
With this patch, we will vectorize all GEPs that haven't already been marked
for scalarization.
The patch refines collectLoopScalars to more exactly identify the scalar GEPs.
The function now more closely resembles collectLoopUniforms. And the patch
moves vector GEP creation out of vectorizeMemoryInstruction and into the main
vectorization loop. The vector GEPs needed for gather and scatter operations
will have already been generated before vectoring the memory accesses.
Original Differential Revision: https://reviews.llvm.org/D30710
llvm-svn: 298735
|
| |
|
|
|
|
|
|
|
|
|
| |
AArch64 doesn't require -mno-red-zone; stack fixups are sufficient here. This was
unnecessarily copied over from the X86 target.
(You can now outline with red zones! Yay!)
Removing the requirement passes all Single/MultiSource tests.
llvm-svn: 298734
|
| |
|
|
| |
llvm-svn: 298733
|
| |
|
|
|
|
|
|
|
| |
Create the constructor in the module pass.
This in needed for the GC-friendly globals change, where the constructor can be
put in a comdat in some cases, but we don't know about that in the function
pass.
llvm-svn: 298731
|
| |
|
|
| |
llvm-svn: 298730
|
| |
|
|
|
|
|
|
|
|
| |
StructurizeCFG can't handle cases with multiple
returns creating regions with multiple exits.
Create a copy of UnifyFunctionExitNodes that only
unifies exit nodes that skips exit nodes
with uniform branch sources.
llvm-svn: 298729
|
| |
|
|
| |
llvm-svn: 298728
|
| |
|
|
| |
llvm-svn: 298727
|
| |
|
|
| |
llvm-svn: 298726
|
| |
|
|
| |
llvm-svn: 298725
|
| |
|
|
|
|
| |
All this did before was assert in EarlyCSE.
llvm-svn: 298724
|
| |
|
|
|
|
|
|
| |
Such instructions sometimes appear after lowering and folding.
Differential Revision: https://reviews.llvm.org/D31318
llvm-svn: 298723
|
| |
|
|
| |
llvm-svn: 298722
|
| |
|
|
|
|
|
|
| |
Previously it was added only to the BE.
Differential Revision: https://reviews.llvm.org/D31323
llvm-svn: 298721
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Summary: Declarations need to be filtered out when counting functions.
Reviewers: eraman
Subscribers: Prazek, llvm-commits
Differential Revision: https://reviews.llvm.org/D31336
llvm-svn: 298720
|