- Apr 01, 2022
-
-
Simon Pilgrim authored
Avoids repeating all the extension/legalization wrapper in every use
-
Alexandros Lamprineas authored
This isn't expected to reduce compilation times as 'max-iters' is set to one by default, but it helps with recursive functions that require higher iteration counts. Differential Revision: https://reviews.llvm.org/D122819
-
Simon Pilgrim authored
[X86] lowerV8I16Shuffle - use explicit SmallVector<SDValue, 4> width to avoid MSVC AVX alignment bug As discussed on Issue #54645 - building llc with /AVX can result in incorrectly aligned structs
-
Groverkss authored
This patch modifies IntegerPolyhedron, IntegerRelation, PresburgerRelation, PresburgerSet, PWMAFunction, constructors to take PresburgerSpace instead of dimensions. This allows information present in PresburgerSpace to be carried better and allows for a general interface. Reviewed By: arjunp Differential Revision: https://reviews.llvm.org/D122842
-
Muhammad Omair Javaid authored
-
Muhammad Omair Javaid authored
TestJobControl.py is randomly failing on AArch64/Arm Linux buildbots. I am marking it as skipped to make buildbot stable.
-
Adrian Kuegel authored
-
Peixin-Qiao authored
This patch supports ordered clause specified without parameter in worksharing-loop directive in the OpenMPIRBuilder and lowering MLIR to LLVM IR. Reviewed By: Meinersbur Differential Revision: https://reviews.llvm.org/D114940
-
Iain Sandoe authored
At present, we are generating wrong code for C++20 modules entities which should have internal linkage. This is because we are assigning 'ModuleInternalLinkage' unconditionally to such entities. However this mode is only applicable to the modules-ts. This change makes the special linkage mode conditional on fmodules-ts and adds a unit test to verify that we generate the correct linkage. Currently, static variables and functions in module purview are emitted into object files as external. On some platforms, lambdas are emitted as global weak defintions (on Windows this causes a mangler crash). Differential Revision: https://reviews.llvm.org/D122413
-
Nikita Popov authored
This reverts commit 09b53121. Breaks the build with GCC 11.2 on x86_64: In file included from /home/npopov/repos/llvm-project/compiler-rt/lib/scudo/scudo_crc32.h:27, from /home/npopov/repos/llvm-project/compiler-rt/lib/scudo/scudo_crc32.cpp:14: /usr/lib/gcc/x86_64-redhat-linux/11/include/smmintrin.h: In function ‘__sanitizer::u32 __scudo::computeHardwareCRC32(__sanitizer::u32, __sanitizer::uptr)’: /usr/lib/gcc/x86_64-redhat-linux/11/include/smmintrin.h:846:1: error: inlining failed in call to ‘always_inline’ ‘long long unsigned int _mm_crc32_u64(long long unsigned int, long long unsigned int)’: target specific option mismatch 846 | _mm_crc32_u64 (unsigned long long __C, unsigned long long __V)
-
Martin Storsjö authored
The pointer.volatile.pass.cpp test was already marked as XFAIL for mingw-dll (for reasons explained in the comment above it). The same issue also appears in clang-cl-dll when built with newer CMake versions. (It didn't appear with older versions of CMake, as CMake built the library with the clang-cl flag `-std:c++latest` when we've requested C++ 20 - which practically built it in c++2b mode with current clang versions. With current versions of CMake, it passes `-std:c++20` instead.) As it succeeds/fails dependent on factors we don't directly control, mark it as UNSUPPORTED instead of XFAIL. Differential Revision: https://reviews.llvm.org/D122718
-
Martin Storsjö authored
Differential Revision: https://reviews.llvm.org/D122800
-
Jason Molenda authored
Many callers of SendPacket() in RNBRemote.cpp have a local std::string object, call c_str() on it to pass a c-string, which is then copied into a std::string temporary object. Also free JSONGenerator objects once we've formatted them into ostringstream and don't need the objects any longer, to reduce max memory use in debugserver. Differential Revision: https://reviews.llvm.org/D122848 rdar://91117263
-
Mehdi Amini authored
Inadvertently removed `populateWithGenerated` while testing native patterns.
-
Chuanqi Xu authored
This solves the multiple defintiion issue https://github.com/llvm/llvm-project/issues/54269. I think the cause of the bug might be an oversight. We just forget to edit this when implementing partitions. And it should be a good fix. Reviewed By: iains Differential Revision: https://reviews.llvm.org/D121271
-
Kees Cook authored
-DLLVM_EXPERIMENTAL_TARGETS_TO_BUILD=CSKY -DLLVM_ENABLE_ASSERTIONS=OFF builds will fail to link due to undefined `llvm::MCInst::dump() const` ``` ld.lld: error: undefined symbol: llvm::MCInst::dump() const >>> referenced by CSKYAsmBackend.cpp >>> /home/kees/src/built-compilers/llvm/stage2-prof-gen/lto.cache/llvmcache-0656FC38C728A7FE0F767D10CD84C7F820114C46:(llvm::CSKYAsmBackend::relaxInstruction(llvm::MCInst&, llvm::MCSubtargetInfo const&) const) ``` Wrap it in LLVM_DEBUG(). Fixes https://github.com/llvm/llvm-project/issues/54684 Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D122854
-
Mehdi Amini authored
This shows that pushing constant to the right in a commutative op leads to `applyPatternsAndFoldGreedily` to converge without applying all the patterns. Differential Revision: https://reviews.llvm.org/D122870
-
Mehdi Amini authored
Revert "[GreedPatternRewriter] Preprocess constants while building worklist when not processing top down" This reverts commit 59bbc7a0. This exposes an issue breaking the contract of `applyPatternsAndFoldGreedily` where we "converge" without applying remaining patterns.
-
Fangrui Song authored
This approach is used by AArch64/RISCV to make frame-setup/frame-destroy instructions contiguous instead of being interleaved by CFI instructions. Code checking `MBBI->getFlag(MachineInstr::FrameSetup) || MBBI->isCFIInstruction()` can be simplified to just check FrameSetup. This helps locate all CFI instructions in the prologue, which can be handy to use .cfi_remember_state/.cfi_restore_state to decrease unwind table size (D114545). Reviewed By: RKSimon Differential Revision: https://reviews.llvm.org/D122541
-
Kai Luo authored
-
Vitaly Buka authored
This UB detected by -fsanitize-memory-use-after-dtor in tensorflow/MLIR.
-
Tan Jinhua authored
Add test cases for coverage_watermark in llvm-cov, also refer to https://reviews.llvm.org/D116876 Differential Revision: https://reviews.llvm.org/D122785
-
Jake Vossen authored
Replace forward slash with backward slash. Reviewed By: kiranchandramohan Differential Revision: https://reviews.llvm.org/D120930
-
Lian Wang authored
Reviewed By: jacquesguan Differential Revision: https://reviews.llvm.org/D122720
-
Richard Smith authored
lexically contains a mention of the pack. Systematically distinguish between syntactic and semantic references to packs, especially when propagating dependence from a type into an expression. We should consult the type-as-written when computing syntactic dependence and should consult the semantic type when computing semantic dependence. Fixes #54402.
-
yanming authored
Add vp.fptoui, vp.uitofp, vp.fptrunc, vp.fpext, vp.trunc, vp.zext, vp.sext, vp.ptrtoint, vp.inttoptr intrinsic and docs. Reviewed By: frasercrmck, craig.topper Differential Revision: https://reviews.llvm.org/D122291
-
Hongtao Yu authored
[llvm-profgen] Fixing a context attribure update issue due to a non-derministic processing order on different platforms. A context can be created by invoking the `getFunctionProfileForContext` function in two ways: - by using a probe and its calling context. - by removing the leaf frame from an existing contexts. The first way is used when generating a function profile for a given LBR range, and the input `WasLeafInlined` is computed depending on the actually probe in the LBR range. The second way is used when using the entry count of an inlinee function profile to update its inliner callsite count, so `WasLeafInlined` is unknown for the inliner frame. The two invocations can happen in different order on different platforms, since the lbr ranges are stored in an unordered_map, and we are making sure `ContextWasInlined` is always set correctly. This should fix the random test failure introduced by D121655 Reviewed By: wenlei Differential Revision: https://reviews.llvm.org/D122844 -
Artur Pilipenko authored
Fix for https://github.com/llvm/llvm-project/issues/51257. Differential Revision: https://reviews.llvm.org/D122601
-
Leonard Grey authored
Differential Revision: https://reviews.llvm.org/D122843
-
Matt Arsenault authored
-
Matt Arsenault authored
-
Matt Arsenault authored
-
Matt Arsenault authored
Avoids use of the default address space parameter, and avoids some assumptions about the incoming address space.
-
Matt Arsenault authored
Use the contextually appropriate value instead of relying on the default address space default parameters. Usually you should be reusing a pre-existing type.
-
LLVM GN Syncbot authored
-
Zequan Wu authored
-
Jorge Gorbe Moya authored
This reverts commit 46774df3.
-
Luboš Luňák authored
Needed at least for -DLLVM_ENABLE_MODULES=On.
-
Shivam authored
-