From: Gottox <Gottox@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] rust: import fix-memory-mf_exec-on-aarch64.patch from alpine
Date: Tue, 05 May 2020 16:17:41 +0200 [thread overview]
Message-ID: <20200505141741.alVw7XeeM3f9gacXzn_PlnTvPuZRBur97Bc70rGwh6M@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21655@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 391 bytes --]
There is an updated pull request by Gottox against master on the void-packages repository
https://github.com/Gottox/void-packages rust-allocation-tests
https://github.com/void-linux/void-packages/pull/21655
rust: import fix-memory-mf_exec-on-aarch64.patch from alpine
addresses buildfail in #21577
A patch file from https://github.com/void-linux/void-packages/pull/21655.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-rust-allocation-tests-21655.patch --]
[-- Type: text/x-diff, Size: 2826 bytes --]
From f5a0bb2a5604f3cf4ca136154af1ddc41ee5a427 Mon Sep 17 00:00:00 2001
From: Enno Boland <gottox@voidlinux.org>
Date: Tue, 5 May 2020 16:15:15 +0200
Subject: [PATCH] rust: import fix-memory-mf_exec-on-aarch64.patch from alpine
addresses buildfail in #21577
---
.../fix-memory-mf_exec-on-aarch64.patch | 27 +++++++++++++++++++
srcpkgs/rust/template | 2 +-
2 files changed, 28 insertions(+), 1 deletion(-)
create mode 100644 srcpkgs/rust/patches/fix-memory-mf_exec-on-aarch64.patch
diff --git a/srcpkgs/rust/patches/fix-memory-mf_exec-on-aarch64.patch b/srcpkgs/rust/patches/fix-memory-mf_exec-on-aarch64.patch
new file mode 100644
index 00000000000..9b7c62c85bd
--- /dev/null
+++ b/srcpkgs/rust/patches/fix-memory-mf_exec-on-aarch64.patch
@@ -0,0 +1,27 @@
+Source: https://git.alpinelinux.org/aports/tree/main/llvm9/fix-memory-mf_exec-on-aarch64.patch
+
+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
+
+--- ./lib/Support/Unix/Memory.inc
++++ ./lib/Support/Unix/Memory.inc
+@@ -59,7 +59,7 @@
+ return PROT_READ | PROT_WRITE | PROT_EXEC;
+ case llvm::sys::Memory::MF_EXEC:
+ #if (defined(__FreeBSD__) || defined(__POWERPC__) || defined (__ppc__) || \
+- defined(_POWER) || defined(_ARCH_PPC))
++ defined(_POWER) || defined(_ARCH_PPC) || (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
diff --git a/srcpkgs/rust/template b/srcpkgs/rust/template
index e7421cf4e04..7438264ff84 100644
--- a/srcpkgs/rust/template
+++ b/srcpkgs/rust/template
@@ -5,7 +5,7 @@
# See: https://github.com/rust-lang/core-team/issues/4
pkgname=rust
version=1.41.1
-revision=2
+revision=3
_rust_dist_version=1.40.0
_cargo_dist_version=0.41.0
# Always make sure custom distfiles used for bootstrap are
next prev parent reply other threads:[~2020-05-05 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 14:16 [PR PATCH] " Gottox
2020-05-05 14:17 ` Gottox [this message]
2020-05-05 17:23 ` jnbr
2020-05-08 22:52 ` [PR PATCH] [Closed]: " q66
2020-05-08 22:52 ` q66
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200505141741.alVw7XeeM3f9gacXzn_PlnTvPuZRBur97Bc70rGwh6M@z \
--to=gottox@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).