diff options
| author | A. Wilcox <AWilcox@Wilcox-Tech.com> | 2022-11-22 01:36:05 -0600 |
|---|---|---|
| committer | A. Wilcox <AWilcox@Wilcox-Tech.com> | 2022-11-22 03:14:38 -0600 |
| commit | cd50a82701f113f26b14850cca88291e77f0a44b (patch) | |
| tree | ef3682081a25f1359cdb40a6c0a399f6d61aa3c0 /legacy/llvm8/fix-memory-mf_exec-on-aarch64.patch | |
| parent | bdd71ef51bdd0b679a1384d3d8cce744ab2c9cc0 (diff) | |
| download | packages-cd50a82701f113f26b14850cca88291e77f0a44b.tar.gz packages-cd50a82701f113f26b14850cca88291e77f0a44b.tar.bz2 packages-cd50a82701f113f26b14850cca88291e77f0a44b.tar.xz packages-cd50a82701f113f26b14850cca88291e77f0a44b.zip | |
user/llvm8: Move to legacy/
We don't need LLVM 8 in-tree any more. The last dependent was Qt
Creator. LLVM 14 is the new hotness.
Closes: #460, #871
Diffstat (limited to 'legacy/llvm8/fix-memory-mf_exec-on-aarch64.patch')
| -rw-r--r-- | legacy/llvm8/fix-memory-mf_exec-on-aarch64.patch | 33 |
1 files changed, 33 insertions, 0 deletions
diff --git a/legacy/llvm8/fix-memory-mf_exec-on-aarch64.patch b/legacy/llvm8/fix-memory-mf_exec-on-aarch64.patch new file mode 100644 index 000000000..a70b39733 --- /dev/null +++ b/legacy/llvm8/fix-memory-mf_exec-on-aarch64.patch @@ -0,0 +1,33 @@ +Fix failures in AllocationTests/MappedMemoryTest.* on aarch64: + + Failing Tests (8): + LLVM-Unit :: Support/./SupportTests/AllocationTests/MappedMemoryTest.AllocAndRelease/3 + LLVM-Unit :: Support/./SupportTests/AllocationTests/MappedMemoryTest.DuplicateNear/3 + LLVM-Unit :: Support/./SupportTests/AllocationTests/MappedMemoryTest.EnabledWrite/3 + LLVM-Unit :: Support/./SupportTests/AllocationTests/MappedMemoryTest.MultipleAllocAndRelease/3 + LLVM-Unit :: Support/./SupportTests/AllocationTests/MappedMemoryTest.SuccessiveNear/3 + LLVM-Unit :: Support/./SupportTests/AllocationTests/MappedMemoryTest.UnalignedNear/3 + LLVM-Unit :: Support/./SupportTests/AllocationTests/MappedMemoryTest.ZeroNear/3 + LLVM-Unit :: Support/./SupportTests/AllocationTests/MappedMemoryTest.ZeroSizeNear/3 + +Upstream-Issue: https://bugs.llvm.org/show_bug.cgi?id=14278#c10 + +--- a/lib/Support/Unix/Memory.inc ++++ b/lib/Support/Unix/Memory.inc +@@ -54,7 +54,7 @@ + llvm::sys::Memory::MF_EXEC: + return PROT_READ | PROT_WRITE | PROT_EXEC; + case llvm::sys::Memory::MF_EXEC: +-#if defined(__FreeBSD__) ++#if defined(__FreeBSD__) || (defined(__linux__) && (defined(__aarch64__) || defined(__powerpc64__))) + // On PowerPC, having an executable page that has no read permission + // can have unintended consequences. The function InvalidateInstruction- + // Cache uses instructions dcbf and icbi, both of which are treated by +@@ -62,6 +62,7 @@ + // executing these instructions will result in a segmentation fault. + // Somehow, this problem is not present on Linux, but it does happen + // on FreeBSD. ++ // The same problem is present even on aarch64 Linux (at least on musl). + return PROT_READ | PROT_EXEC; + #else + return PROT_EXEC; |