diff options
author | Natanael Copa <ncopa@alpinelinux.org> | 2018-06-06 13:50:48 +0000 |
---|---|---|
committer | Natanael Copa <ncopa@alpinelinux.org> | 2018-06-06 13:51:46 +0000 |
commit | ee1d69cb00ec768fc2d3b5b63597b351475393e0 (patch) | |
tree | cb5eb66ed5092a1b407ec49d67c875d34aaaf417 /community/llvm3.9/fix-memory-mf_exec-on-aarch64.patch | |
parent | b007fd689eb3bdc8520590b1956241e997016233 (diff) | |
download | aports-ee1d69cb00ec768fc2d3b5b63597b351475393e0.tar.bz2 aports-ee1d69cb00ec768fc2d3b5b63597b351475393e0.tar.xz |
unmaintained/llvm3.9: move from community
only julia was using it
Diffstat (limited to 'community/llvm3.9/fix-memory-mf_exec-on-aarch64.patch')
-rw-r--r-- | community/llvm3.9/fix-memory-mf_exec-on-aarch64.patch | 33 |
1 files changed, 0 insertions, 33 deletions
diff --git a/community/llvm3.9/fix-memory-mf_exec-on-aarch64.patch b/community/llvm3.9/fix-memory-mf_exec-on-aarch64.patch deleted file mode 100644 index 644c77790a..0000000000 --- a/community/llvm3.9/fix-memory-mf_exec-on-aarch64.patch +++ /dev/null @@ -1,33 +0,0 @@ -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__)) - // 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; |