From: Asuna Yang <spriteovo@gmail.com>
To: "Conor Dooley" <conor@kernel.org>,
"Jason Montleon" <jmontleo@redhat.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <lossin@kernel.org>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Trevor Gross" <tmgross@umich.edu>,
"Danilo Krummrich" <dakr@kernel.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Alexandre Ghiti" <alex@ghiti.fr>
Cc: rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-riscv@lists.infradead.org, Asuna Yang <SpriteOvO@gmail.com>
Subject: RISC-V: Re-enable GCC+Rust builds
Date: Sat, 30 Aug 2025 13:00:56 +0800 [thread overview]
Message-ID: <68496eed-b5a4-4739-8d84-dcc428a08e20@gmail.com> (raw)
I noticed that GCC+Rust builds for RISC-V were disabled about a year
ago, as discussed in
https://lore.kernel.org/all/20240917000848.720765-1-jmontleo@redhat.com/
I'm a bit lost here. What are the main obstacles to re-enabling GCC
builds now?
Conor said:
> Okay. Short term then is deny gcc + rust, longer term is allow it
with the same caveats as the aforementioned mixed stuff.
"the same caveats" means detecting what specifically?
We have a RISC-V PWM driver being written in Rust. Currently, GCC being
disabled for building the kernel with Rust for RISC-V is the primary
blocker for including these drivers in RISC-V distros. Therefore, I'd
like to push forward and contribute to the re-enabling of GCC builds. Is
there a more detailed direction on what I can do here?
Thanks.
next reply other threads:[~2025-08-30 5:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 5:00 Asuna Yang [this message]
2025-08-30 18:17 ` Conor Dooley
2025-09-01 14:08 ` Conor Dooley
2025-09-01 17:19 ` Asuna
2025-09-01 18:04 ` Conor Dooley
2025-09-03 0:59 ` Asuna
2025-09-04 11:28 ` Conor Dooley
2025-09-03 18:52 ` Asuna
2025-09-03 19:07 ` [PATCH 1/2] rust: get the version of libclang used by bindgen in a separate script Asuna Yang
2025-09-03 19:07 ` [PATCH 2/2] RISC-V: re-enable gcc + rust builds Asuna Yang
2025-09-03 23:27 ` Miguel Ojeda
2025-09-04 23:17 ` Asuna
2025-09-04 12:27 ` Conor Dooley
2025-09-04 22:56 ` Asuna
2025-09-04 23:07 ` Asuna
2025-09-05 15:25 ` Conor Dooley
2025-09-05 15:24 ` Conor Dooley
2025-09-05 15:28 ` Conor Dooley
2025-09-03 23:24 ` [PATCH 1/2] rust: get the version of libclang used by bindgen in a separate script Miguel Ojeda
2025-09-04 23:15 ` Asuna
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=68496eed-b5a4-4739-8d84-dcc428a08e20@gmail.com \
--to=spriteovo@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=alex@ghiti.fr \
--cc=aliceryhl@google.com \
--cc=aou@eecs.berkeley.edu \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=conor@kernel.org \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=jmontleo@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
/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
all inboxes | Powered by JetHome®