bcm5719-llvm/llvm/test/CodeGen, branch meklort-10.0.1Project Ortega BCM5719 LLVMhttps://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.12020-07-07T16:21:37+00:00[tests] Revert unhelpful change from d73eed42d1dc2020-07-07T16:21:37+00:00Hubert Tonghubert.reinterpretcast@gmail.com2020-05-01T02:18:54+00:00urn:sha1:ef32c611aa214dea855364efd7ba451ec5ec3f74
(cherry picked from commit 0e8608b3c38886c224d252c6b126c804645b7761)
[tests] Speculative fix for buildbot breakage from c5f7c039efe72020-07-06T22:40:20+00:00Hubert Tonghubert.reinterpretcast@gmail.com2020-05-01T02:04:02+00:00urn:sha1:70919a46facce7f232cf8bc1f2e4b6455abe01d5
(cherry picked from commit d73eed42d1dcba06a5b793346f6e3eed0c7f41ac)
[DAGCombine] Check the uses of negated floating constant and remove the hack2020-06-26T20:45:41+00:00QingShan Zhangqshanz@cn.ibm.com2020-03-05T03:42:50+00:00urn:sha1:76ceebb0d96361de2b61bf8e504d306d1f2e492f
PowerPC hits an assertion due to somewhat the same reason as https://reviews.llvm.org/D70975.
Though there are already some hack, it still failed with some case, when the operand 0 is NOT
a const fp, it is another fma that with const fp. And that const fp is negated which result in multi-uses.
A better fix is to check the uses of the negated const fp. If there are already use of its negated
value, we will have benefit as no extra Node is added.
Differential revision: https://reviews.llvm.org/D75501
(cherry picked from commit 3906ae387f0775dfe4426e4336748269fafbd190)
[PPCAsmPrinter] support 'L' output template for memory operands2020-06-25T23:19:39+00:00Nick Desaulniersndesaulniers@google.com2020-06-15T21:21:55+00:00urn:sha1:b294e611271abeb5c9c49d7fb216b9bdcc323872
Summary:
L is meant to support the second word used by 32b calling conventions for 64b arguments.
This is required for build 32b PowerPC Linux kernels after upstream
commit 334710b1496a ("powerpc/uaccess: Implement unsafe_put_user() using 'asm goto'")
Thanks for the report from @nathanchance, and reference to GCC's
implementation from @segher.
Fixes: pr/46186
Fixes: https://github.com/ClangBuiltLinux/linux/issues/1044
Reviewers: echristo, hfinkel, MaskRay
Reviewed By: MaskRay
Subscribers: MaskRay, wuzish, nemanjai, hiraditya, kbarton, steven.zhang, llvm-commits, segher, nathanchance, srhines
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D81767
(cherry picked from commit 2d8e105db6bea10a6b96e4a094e73a87987ef909)
[AArch64] Change AArch64 Windows EH UnwindHelp object to be a fixed object2020-06-25T23:19:14+00:00Daniel FramptonDaniel.Frampton@microsoft.com2020-03-31T20:12:54+00:00urn:sha1:a110c3fc8cd9368627ce0386d7d16756be3d62ac
The UnwindHelp object is used during exception handling by runtime
code. It must be findable from a fixed offset from FP.
This change allocates the UnwindHelp object as a fixed object (as is
done for x86_64) to ensure that both the generated code and runtime
agree on the location of the object.
Fixes https://bugs.llvm.org/show_bug.cgi?id=45346
Differential Revision: https://reviews.llvm.org/D77016
(cherry picked from commit 494abe139a9aab991582f1b3f3370b99b252944c)
[AArch64] Fix mismatch in prologue and epilogue for funclets on Windows2020-06-25T23:19:14+00:00Daniel FramptonDaniel.Frampton@microsoft.com2020-03-31T20:11:16+00:00urn:sha1:69fb858731e857abcabe74dcf6db344030ca650b
The generated code for a funclet can have an add to sp in the epilogue
for which there is no corresponding sub in the prologue.
This patch removes the early return from emitPrologue that was
preventing the sub to sp, and instead conditionalizes the appropriate
parts of the rest of the function.
Fixes https://bugs.llvm.org/show_bug.cgi?id=45345
Differential Revision: https://reviews.llvm.org/D77015
(cherry picked from commit 522b4c4b88a5606b0074926e8658e7fede97c230)
[RISCV] Fix incorrect FP base CFI offset for variable argument functions2020-06-25T23:13:53+00:00Shiva Chenshiva@andestech.com2020-02-03T05:52:13+00:00urn:sha1:43ca67c05d2881d00075a15de555af1b19370294
When the FP exists, the FP base CFI directive offset should take the size of variable arguments into account.
Differential Revision: https://reviews.llvm.org/D73862
(cherry picked from commit 64f417200e1020305f28f3c1e40691585f50f6ad)
[RISCV64] Emit correct lib call for fp(float/double) to ui/si2020-06-25T23:13:53+00:00Kamlesh Kumarkamleshbhalui@gmail.com2020-06-18T13:46:54+00:00urn:sha1:249fef00d925ce56d7eb1f6910064a586716cba4
Since i32 is not legal in riscv64,
it always promoted to i64 before emitting lib call and
for conversions like float/double to int and float/double to unsigned int
wrong lib call was emitted. This commit fix it using custom lowering.
Differential Revision: https://reviews.llvm.org/D80526
(cherry picked from commit 7622ea5835f0381a426e504f4c03f11733732b83)
[LegalizeTypes][RISCV] Correctly sign-extend comparison for ATOMIC_CMP_XCHG2020-06-25T23:13:53+00:00Alex Bradburyasb@asbradbury.org2020-06-25T10:38:33+00:00urn:sha1:f8e49af4f1adcf457ea32e7164a126b10357cf4f
Currently, the comparison argument used for ATOMIC_CMP_XCHG is legalised
with GetPromotedInteger, which leaves the upper bits of the value
undefind. Since this is used for comparing in an LR/SC loop with a
full-width comparison, we must sign extend it on RISC-V.
This is related to https://reviews.llvm.org/D58829, which solved the
issue for ATOMIC_CMP_SWAP_WITH_SUCCESS, but not the simpler
ATOMIC_CMP_SWAP.
This patch is a modified form of
616289ed29225c0ddfe5699c7fdf42a0fcbe0ab4 by Jessica Clarke. It localises
the changes to LegalizeIntegerTypes and avoids adding a new virtual
method to TargetLowering to avoid changing the ABI of libLLVM.so.
fixed broken test after cherry pick2020-06-24T16:31:04+00:00Scott Constablescott.d.constable@intel.com2020-06-18T03:02:08+00:00urn:sha1:d24d5c8e308e689dcd83cbafd2e8bd32aa845a15