diff options
| author | J0WI <J0WI@users.noreply.github.com> | 2019-02-27 00:02:32 +0100 |
|---|---|---|
| committer | Natanael Copa <ncopa@alpinelinux.org> | 2019-03-19 10:14:05 +0000 |
| commit | db695fa462a77934f2c6f4ee835ad46963ad35c2 (patch) | |
| tree | 82d1c3defc1cac17ab22b83e7aaa2e845eb96554 /testing/llvm6/fix-memory-mf_exec-on-aarch64.patch | |
| parent | b797f720d78062467908325d04f1c0b5c38f891f (diff) | |
| download | aports-db695fa462a77934f2c6f4ee835ad46963ad35c2.tar.bz2 aports-db695fa462a77934f2c6f4ee835ad46963ad35c2.tar.xz | |
testing/llvm6: new aport
Diffstat (limited to 'testing/llvm6/fix-memory-mf_exec-on-aarch64.patch')
| -rw-r--r-- | testing/llvm6/fix-memory-mf_exec-on-aarch64.patch | 33 |
1 files changed, 33 insertions, 0 deletions
diff --git a/testing/llvm6/fix-memory-mf_exec-on-aarch64.patch b/testing/llvm6/fix-memory-mf_exec-on-aarch64.patch new file mode 100644 index 0000000000..644c77790a --- /dev/null +++ b/testing/llvm6/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__)) + // 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; |