- Nov 08, 2020
-
-
Sanjay Patel authored
-
Simon Pilgrim authored
-
Simon Pilgrim authored
-
Simon Pilgrim authored
-
Simon Pilgrim authored
Just use default CHECK
-
Simon Pilgrim authored
Just use default CHECK in most cases.
-
Simon Pilgrim authored
Just use default CHECK
-
Simon Pilgrim authored
We were relying on the dyn_cast<> succeeding - better use cast<> and have it assert that its the correct type than dereference a null result.
-
Simon Pilgrim authored
We were relying on the dyn_cast<> succeeding - better use cast<> and have it assert that its the correct type than dereference a null result.
-
Simon Pilgrim authored
As raised by @nlopes on D90382 - if this is not a rotate then the select was blocking poison from the 'shift-by-zero' non-TVal, but a funnel shift won't - so freeze it.
-
Simon Pilgrim authored
We can just check for a null value.
-
Florian Hahn authored
This fixes a crash when trying to get a SCEV expression for operands that are not SCEV-able.
-
Pedro Tammela authored
This patch refactors the pass to accomodate the new pass manager boilerplate. Differential Revision: https://reviews.llvm.org/D91005
-
Arthur Eubanks authored
This reverts commit ae385400. As well as some follow-up test fixes. The original change causes new-pass-manager.ll to fail when polly is enabled.
-
Craig Topper authored
Invert the select condition when masking in the sign bit of a fptoui operation. Also, rather than lowering the sign mask to select/xor and expecting the select to get cleaned up later, directly lower to shift/xor. Patch by Layton Kifer! Reviewed By: craig.topper Differential Revision: https://reviews.llvm.org/D90658
-
Craig Topper authored
[RISCV] Remove assertsexti32 from a couple B extension isel patterns that don't demanded the sign extended bits.
-
Alexander Shaposhnikov authored
Move the implementation of getStringTableBuilderKind into MachOLayoutBuilder.cpp. NFC. Test plan: make check-all
-
Fangrui Song authored
The pattern should patch `a.a(a.o)` instead of `a.a`
-
Fangrui Song authored
-
Kazu Hirata authored
-
Kazu Hirata authored
-
Stella Laurenzo authored
* Wires them in the same way that peer-dialect test passes are registered. * Fixes the build for -DLLVM_INCLUDE_TESTS=OFF. Differential Revision: https://reviews.llvm.org/D91022
-
Cornelius Aschermann authored
This diff fixes missing fields initialization (Size, VMSize). Previously this resulted in broken binaries when multiple sections were added in one tool's invocatation. Test plan: make check-all Differential revision: https://reviews.llvm.org/D90690
-
Carl Ritson authored
Fix a crash when SCC is defined until end of block and mode change must be inserted in SCC live region. Reviewed By: mceier Differential Revision: https://reviews.llvm.org/D90997
-
Mehdi Amini authored
-
Stephen Kelly authored
This was missing from commit 7efe07a1 (Traverse-ignore explicit template instantiations, 2020-11-06).
-
Craig Topper authored
[RISCV] Add test cases showing missed opportunities to use sbset/sbclr/sbinv/sbext when the shift amount isn't masked to log2(xlen) bits. NFC Out of bounds shifts are undefined and these instructions mask their shift amount before use. So we don't need to see a mask in order to select the instructions.
-
Renato Golin authored
As discussed in the mailing list [1-4], we need a separation of support tiers when requiring support from the whole community versus a sub-community. Essentially, if a sub-community is active enough and takes maintenance into their own internal costs without affecting other parts of the community's maintenance costs, then code that is not immediately relevant to all parts (ie. not released, actively tested, etc) can still find its way into the LLVM main repository without major pain points. The main benefit is to reduce the maintenance cost that those sub-communities have outside of LLVM (for example, in duplicating common code, applying the same patches on top of multiple user repositories or downstream projects). This document outlines the components and responsibilities of the sub-communities with regards to maintenance costs and how they affect the rest of the community. It also adds an addendum on removal policies, which expand the existing "new target removal" policy into something more generic, to encompass any piece of code, scripts or documents in the repository. [1] http://lists.llvm.org/pipermail/llvm-dev/2020-October/146249.html [2] http://lists.llvm.org/pipermail/llvm-dev/2020-November/146335.html [3] http://lists.llvm.org/pipermail/llvm-dev/2020-October/146138.html [4] http://lists.llvm.org/pipermail/llvm-dev/2020-November/146298.html
-
Craig Topper authored
-
LLVM GN Syncbot authored
-
Nathan James authored
The config providers that look for configuration files currently take a pointer to a FileSystem in the constructor. For some reason this isn't actually used when trying to read those configuration files, Essentially it just follows the behaviour of the real filesystem. Using clang-tidy standalone this doesn't cause any issue. But if its used as a library and the user wishes to use say an `InMemoryFileSystem` it will try to read the files from the disc instead. Reviewed By: aaron.ballman Differential Revision: https://reviews.llvm.org/D90992
-
Mehdi Amini authored
-
Mehdi Amini authored
-
Jonas Devlieghere authored
Convert analyzeContextInfo to a work list using the same approach I used to remove the recursion from lookForDIEsToKeep. This fixes the crash reported in https://llvm.org/PR48029. Tested using the reproducer attached to PR48029 as well as by comparing the clang MD5 hashes before and after the change (with and without gmodules). Differential revision: https://reviews.llvm.org/D90873
-
Michał Górny authored
Use skipUnlessDarwin decorator for tests that are specific to Darwin, instead of skipIf... for all other platforms. This should make it clear that these tests are not supposed to work elsewhere. It will also make these tests stop repeatedly popping up while I look for tests that could be fixed on the platform in question. Differential Revision: https://reviews.llvm.org/D91003
-
Michał Górny authored
-
Stella Laurenzo authored
This reverts commit 33039805. Differential Revision: https://reviews.llvm.org/D91006
-
Nikita Popov authored
The distinction between StructOffset and OtherOffset has been originally introduced by 82069c44, which applied different reasoning to both offset kinds. However, this distinction was not actually correct, and has been fixed by c84e77ae. Since then, we only ever consider the sum StructOffset + OtherOffset, so we may as well store it in that form directly.
-
Stella Laurenzo authored
* Introduced issue in debug builds. This reverts commit b5fcd061.
-
Nikita Popov authored
Instead of performing the multiplication in double the bit width and using active bits to determine overflow, use the existing smul_ov() APInt method to detect overflow. The smul_ov() implementation is not particularly efficient, but it's still better than doing this a wide, usually 128-bit, type.
-