From: Jamie Cunliffe <Jamie.Cunliffe@arm.com>
To: linux-arm-kernel@lists.infradead.org, rust-for-linux@vger.kernel.org
Cc: Miguel Ojeda <ojeda@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
steve.capper@arm.com, Asahi Lina <lina@asahilina.net>,
boqun.feng@gmail.com
Subject: [PATCH v3 0/1] Rust enablement for AArch64
Date: Mon, 16 Oct 2023 14:15:22 +0100 [thread overview]
Message-ID: <20231016131523.1521965-1-Jamie.Cunliffe@arm.com> (raw)
Enable Rust support for the AArch64 architecture.
The only change here since the v2 patch is the removal of the
fp-armv8 feature. rustc ties fp and Neon together. However due to a
bug in versions before 1.71 fp wasn't correctly being disabled. Now
the compiler version used is 1.71 we can drop this option which now
allows this to build without warnings.
Jamie Cunliffe (1):
arm64: rust: Enable Rust support for AArch64
Documentation/rust/arch-support.rst | 1 +
Makefile | 1 -
arch/arm64/Kconfig | 1 +
arch/arm64/Makefile | 4 ++++
arch/x86/Makefile | 1 +
rust/Makefile | 6 +++++-
scripts/Makefile | 5 +++--
scripts/generate_rust_target.rs | 4 +++-
8 files changed, 18 insertions(+), 5 deletions(-)
--
2.30.2
next reply other threads:[~2023-10-16 13:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 13:15 Jamie Cunliffe [this message]
2023-10-16 13:15 ` [PATCH v3 1/1] arm64: rust: Enable Rust support for AArch64 Jamie Cunliffe
2023-10-16 18:14 ` Boqun Feng
2023-10-16 21:47 ` Andrew Lunn
2023-10-17 9:24 ` Miguel Ojeda
2023-10-17 9:27 ` Miguel Ojeda
2023-10-17 15:38 ` Miguel Ojeda
2023-10-17 17:47 ` Miguel Ojeda
2023-10-19 14:41 ` Will Deacon
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=20231016131523.1521965-1-Jamie.Cunliffe@arm.com \
--to=jamie.cunliffe@arm.com \
--cc=boqun.feng@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=lina@asahilina.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=steve.capper@arm.com \
--cc=will@kernel.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).