Project Ortega BCM5719 LLVM https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1 2020-06-25T23:19:14+00:00 2020-06-25T23:19:14+00:00 Daniel Frampton Daniel.Frampton@microsoft.com 2020-03-31T20:12:54+00:00 urn: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) 2020-06-25T23:19:14+00:00 Daniel Frampton Daniel.Frampton@microsoft.com 2020-03-31T20:11:16+00:00 urn: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) 2020-06-17T22:37:19+00:00 Wei Zhao wxz@marvell.com 2020-05-13T23:38:42+00:00 urn:sha1:f5a9c661a35621640370837bae67cfb28f2f279b This is the first checkin to support Marvell ThunderX3T110. Initial definition of the micro-ops of the instructions in ThunderX3T110 is included. Differential Revision: https://reviews.llvm.org/D78129 (cherry picked from commit 382d3a85e2a9269569e7fb8caa487d7ef57900c6) 2020-06-17T03:05:15+00:00 Daniel Kiss daniel.kiss@arm.com 2020-06-15T13:02:38+00:00 urn:sha1:bf89c5aeb8915d488fa1c790e1b237b62a49c01f Summary: SCTLR_EL1.BT[01] controls the PACI[AB]SP compatibility with PBYTE 11 (see [1]) This bit will be set to zero so PACI[AB]SP are equal to BTI C instruction only. [1] https://developer.arm.com/docs/ddi0595/b/aarch64-system-registers/sctlr_el1 Reviewers: chill, tamas.petz, pbarrio, ostannard Reviewed By: tamas.petz, ostannard Subscribers: kristof.beyls, hiraditya, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D81746 (cherry picked from commit b8ae3fdfa579dbf366b1bb1cbfdbf8c51db7fa55) 2020-06-17T03:05:14+00:00 Daniel Kiss daniel.kiss@arm.com 2020-02-13T10:42:39+00:00 urn:sha1:aab50695971617d37ad420b476671995f7078e79 In some cases BTI landing pad is inserted even compatible instruction was there already. Meta instruction does not count in this case therefore skip them in the check for first instructions in the function. Differential revision: https://reviews.llvm.org/D74492 (cherry picked from commit d5a186a60014dc1a8c979c978cb32aba7ecb9102) 2020-02-28T10:52:11+00:00 serge-sans-paille sguelton@redhat.com 2020-02-21T14:51:19+00:00 urn:sha1:cd0926d087a85c5ee1222ca80980b4440214a822 According to Joseph Myers, a libm maintainer > They were only ever an ABI (selected by use of -ffinite-math-only or > options implying it, which resulted in the headers using "asm" to redirect > calls to some libm functions), not an API. The change means that ABI has > turned into compat symbols (only available for existing binaries, not for > anything newly linked, not included in static libm at all, not included in > shared libm for future glibc ports such as RV32), so, yes, in any case > where tools generate direct calls to those functions (rather than just > following the "asm" annotations on function declarations in the headers), > they need to stop doing so. As a consequence, we should no longer assume these symbols are available on the target system. Still keep the TargetLibraryInfo for constant folding. Differential Revision: https://reviews.llvm.org/D74712 (cherry picked from commit 6d15c4deab51498b70825fb6cefbbfe8f3d9bdcf) For https://bugs.llvm.org/show_bug.cgi?id=45034 2020-02-26T14:22:28+00:00 Roman Lebedev lebedev.ri@gmail.com 2020-02-25T17:08:58+00:00 urn:sha1:3abd9cd486d9c45867458f64d1294db698c39b4e This reverts https://reviews.llvm.org/D58468 (rL354676, 44037d7a6377ec8e5542cced73583283334b516b), and all and any follow-ups to that code block. https://bugs.llvm.org/show_bug.cgi?id=43446 (cherry picked from commit d20907d1de89bf63b589fadd8c096d4895e47fba) 2020-02-18T15:46:44+00:00 Diogo Sampaio diogo.sampaio@arm.com 2020-02-15T05:05:15+00:00 urn:sha1:b5d9a7e72fafaead89f0cc8994925c90ed3169be Summary: When using strict fp, it is required to update the chain when performing integer type promotion of a operand to a integer to floating point conversion. Reviewers: craig.topper, john.brawn Reviewed By: craig.topper Subscribers: kristof.beyls, hiraditya, llvm-commits Tags: #llvm Differential Revision: https://reviews.llvm.org/D74597 (cherry picked from commit 8bc790f9e6a6fc6d8fe8f41a7120269366fa0957) 2020-02-18T15:46:42+00:00 John Brawn john.brawn@arm.com 2020-01-28T14:04:09+00:00 urn:sha1:cff417cffd61d2c4607eb142e272ec10ebec2c21 These get lowered to function calls, like the non-strict versions. Differential Revision: https://reviews.llvm.org/D73784 (cherry picked from commit 68cf574857c81f711f498a479855a17e7bea40f7) 2020-02-18T15:46:40+00:00 John Brawn john.brawn@arm.com 2020-01-27T15:51:06+00:00 urn:sha1:fca6c5e5dbf283b9e96b4a6ba8d343ff5dd91328 Strict fp-to-int and int-to-fp conversions can be handled in the same way that the non-strict versions are (by using the appropriate instruction or converting to a function call when we have no instruction). Differential Revision: https://reviews.llvm.org/D73625 (cherry picked from commit 0bb9a27c9895c0fbc3f55f56ad7f1e1927398fce)