- Aug 10, 2021
-
-
Lang Hames authored
Darwin/MachO TLV support was only getting built into the x86_64 slice, not the x86_64h slice. This caused errors when using the ORC runtime on Haswell machines. rdar://81056700
-
Jean Perier authored
https://reviews.llvm.org/D105464 did not correctly cover the case where the symbol from the host procedure is use associated. Outside of the mis-parsed ArrayRef case, flang was also creating a symbol with HostAssociated details inside the internal procedure (pointing to the use associated symbol in the host). That is what lowering expects. This patch ensures the same logic is applied in the mis-parsed array-ref name resolution (and the pointer target name resolution). Differential Revision: https://reviews.llvm.org/D107759
-
Carl Ritson authored
Avoid stack overflow errors on systems with small stack sizes by removing recursion in FoldCondBranchOnPHI. This is a simple change as the recursion was only iteratively calling the function again on the same arguments. Ideally this would be compiled to a tail call, but there is no guarantee. Reviewed By: lebedev.ri Differential Revision: https://reviews.llvm.org/D107803
-
Fraser Cormack authored
This patch aims to clear up any confusion in documentation for the fadd/fmul reduction creation APIs with regards to the sequential and unordered variations without changing the APIs themselves. The scalar accumulator value isn't only used for sequential reduction intrinsics so the impliciation to the contrary was dropped. Then I thought it useful to make clear that the API always creates a sequential reduction. And lastly a note to users on how it is possible to transform the resulting reduction into an unordered one. Reviewed By: craig.topper Differential Revision: https://reviews.llvm.org/D107753
-
Ben Dunbobbin authored
We had coverage of empty archive in our downstream testsuite. This adds those cases upstream. Differential Revision: https://reviews.llvm.org/D107471
-
Ben Dunbobbin authored
This adds thin archives to the map file test. I noticed that we had this test-case in our downstream testsuite but it wasn't in the upstream testing. Differential revision: https://reviews.llvm.org/D107555
-
Archibald Elliott authored
D105263 introduced this new test. It fails when asserts are disabled, due to using a debug option on opt. Reviewed By: pengfei Differential Revision: https://reviews.llvm.org/D107805
-
David Green authored
This changes a couple of calls to LiveRegs.contains to !LiveRegs.available, one in Thumb1FrameLoweringInfo (which modifies a test to look more correct to me, given r7 should be the frame pointer so is not available), and another in the ARMLoadStoreOptimizer, that I don't have a test for, it was just found by inspection. Differential Revision: https://reviews.llvm.org/D107454
-
Tony Tye authored
C++20 no longer requires the failure memory ordering to be no stronger than the success memory ordering. Adjust assert in AMD GPU SIMemoryLegalizer, and merge instruction memory orderings Add common operation to merge memory orders that allows non strict memory orderings to be combined. Use it in SIMemoryLegalizer and MachineMemOperand::getMergedOrdering. Reviewed By: efriedma, rampitec Differential Revision: https://reviews.llvm.org/D106729
-
Florian Mayer authored
We would put the return address there, rather than the fault address. Reviewed By: eugenis Differential Revision: https://reviews.llvm.org/D107578
-
David Sherwood authored
I have updated cheapToScalarize to also consider the case when extracting lanes from a stepvector intrinsic. This required removing the existing 'bool IsConstantExtractIndex' and passing in the actual index as a Value instead. We do this because we need to know if the index is <= known minimum number of elements returned by the stepvector intrinsic. Effectively, when extracting lane X from a stepvector we know the value returned is also X. New tests added here: Transforms/InstCombine/vscale_extractelement.ll Differential Revision: https://reviews.llvm.org/D106358
-
Vitaly Buka authored
-
Vitaly Buka authored
Without interceptor implementation may call strlen on internal buffers causing false msan errors. Differential Revision: https://reviews.llvm.org/D107615
-
Martin Storsjö authored
This one already had a proper explanation why it fails, which is due to differences by design in MSVC mode. This isn't a fixme, so degrade the annotation to a more permanent "XFAIL: msvc" instead. Differential Revision: https://reviews.llvm.org/D107758
-
Martin Storsjö authored
Such environments do have aligned allocation functions these days, but the RTTI type name test needs to be adjusted for the MSVC C++ ABI. Differential Revision: https://reviews.llvm.org/D107757
-
Martin Storsjö authored
This allows waiving the right amount of asserts on Windows and zOS. This should supersede D107124 and D105910. Differential Revision: https://reviews.llvm.org/D107755
-
Cullen Rhodes authored
Reviewed By: paulwalker-arm Differential Revision: https://reviews.llvm.org/D107752
-
David Sherwood authored
This patch updates ConstantVector::getSplat to use poison instead of undef when using insertelement/shufflevector to splat. This follows on from D93793. Differential Revision: https://reviews.llvm.org/D107751
-
Tres Popp authored
Replace some code snippets With scf::ForOp methods. Additionally, share a listener at one more point (although this pattern is still not safe to roll back currently) Differential Revision: https://reviews.llvm.org/D107754
-
LLVM GN Syncbot authored
-
Wang, Pengfei authored
1. Enable FP16 type support and basic declarations used by following patches. 2. Enable new instructions VMOVW and VMOVSH. Ref.: https://software.intel.com/content/www/us/en/develop/download/intel-avx512-fp16-architecture-specification.html Reviewed By: LuoYuanke Differential Revision: https://reviews.llvm.org/D105263
-
Fangrui Song authored
Reviewed By: benshi001, mhjacobson Differential Revision: https://reviews.llvm.org/D107797
-
Matthias Springer authored
The following constructor call (and others) used to be ambiguous: ``` FlatAffineConstraints constraints(0, 0, 0); ``` Differential Revision: https://reviews.llvm.org/D107726
-
Matthias Springer authored
This is in preparation of a larger refactoring that makes the changes in D107221 obsolete. Differential Revision: https://reviews.llvm.org/D107724
-
Ettore Tiotto authored
Code added by D106688 has a problem. It passes the option -bxyz to the system linker as -b xyz xyz (duplication of the string 'xyz' is incorrect). This patch fixes that oversight. Reviewed by: hubert.reinterpretcast, jsji Differential Revision: https://reviews.llvm.org/D107786
-
Anshil Gandhi authored
This patch allows target specific addr space in target builtins for HIP. It inserts implicit addr space cast for non-generic pointer to generic pointer in general, and inserts implicit addr space cast for generic to non-generic for target builtin arguments only. It is NFC for non-HIP languages. Differential Revision: https://reviews.llvm.org/D102405
-
LLVM GN Syncbot authored
-
zoecarver authored
Differential Revision: https://reviews.llvm.org/D107096
-
Louis Dionne authored
That's not necessary anymore, since we always build the dylib with C++11 capabilities nowadays. Differential Revision: https://reviews.llvm.org/D107772
-
Usman Nadeem authored
Replace vector unpack operation with a scalar extend operation. unpack(splat(X)) --> splat(extend(X)) If we have both, unpkhi and unpklo, for the same vector then we may save a register in some cases, e.g: Hi = unpkhi (splat(X)) Lo = unpklo(splat(X)) --> Hi = Lo = splat(extend(X)) Differential Revision: https://reviews.llvm.org/D106929 Change-Id: I77c5c201131e3a50de1cdccbdcf84420f5b2244b
-
Usman Nadeem authored
Move the last{a,b} operation to the vector operand of the binary instruction if the binop's operand is a splat value. This essentially converts the binop to a scalar operation. Example: // If x and/or y is a splat value: lastX (binop (x, y)) --> binop(lastX(x), lastX(y)) Differential Revision: https://reviews.llvm.org/D106932 Change-Id: I93ff5302f9a7972405ee0d3854cf115f072e99c0 -
Michał Górny authored
Add a LLVM_LIT_ARGS cached variable in order to make it possible to override lit arguments when doing standalone builds. Without that, the user variable is ignored and the default options are always used. Based on a similar solution found in clang. Differential Revision: https://reviews.llvm.org/D107700
-
David Goldman authored
Xcode uses `#pragma mark -` to draw a divider in the outline view and `#pragma mark Note` to add `Note` in the outline view. For more information, see https://nshipster.com/pragma/. Since the LSP spec doesn't contain dividers for the symbol outline, instead we treat `#pragma mark -` as a group with children - the decls that come after it, implicitly terminating when the symbol's parent ends. The following code: ``` @implementation MyClass - (id)init {} - (int)foo; @end ``` Would give an outline like ``` MyClass > Overrides > init > Public Accessors > foo ``` Differential Revision: https://reviews.llvm.org/D105904
-
Alexander Belyaev authored
Original change by pifon@pifon:tfrt_clean:6896:citc on 2021/08/09 05:30:17. Ad b Differential Revision: https://reviews.llvm.org/D107762
-
Aart Bik authored
Looks "under the hood" of the sparse stogage schemes. Users should typically not be interested in these details (hey, that is why we have "sparse compilers"!) but this test makes sure the compact contents are as expected. Reviewed By: ThomasRaoux, bixia Differential Revision: https://reviews.llvm.org/D107683
-
Michał Górny authored
Some LD_PRELOAD-ed libraries tend to interact badly with --nodefaultlib, particularly Gentoo sandbox. Do not run this test if LD_PRELOAD is present in the running environment. Differential Revision: https://reviews.llvm.org/D107701
-
Louis Dionne authored
This patch fixes the constrains on the __perfect_forward constructor and its call operators, which were incorrect. In particular, it makes sure that we closely follow [func.require], which basically says that we must deliver the bound arguments with the appropriate value category or make the call ill-formed, but not silently fall back to using a different value category. As a fly-by, this patch also: - Adds types __bind_front_t and __not_fn_t to make the result of calling bind_front and not_fn more opaque, and improve diagnostics for users. - Adds a bunch of tests for bind_front and remove some that are now redundant. - Adds some missing _LIBCPP_HIDE_FROM_ABI annotations. Immense thanks to @tcanens for raising awareness about this issue, and providing help with the = delete bits. Differential Revision: https://reviews.llvm.org/D107199
-
Louis Dionne authored
We just had a case where a build bot stalled in an infinite loop during testing, and the whole pipeline got stuck. To avoid that from happening in the future, use a timeout on BuildKite jobs. Differential Revision: https://reviews.llvm.org/D107765
-
Paul Robinson authored
This reverts commit 187c69e9. compiler-rt/test/cross_over_uniform_dist.test refuses to pass.
-
Paul Robinson authored
This reverts commit dc11e69d. The speculative fix did not help.
-