[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <68496eed-b5a4-4739-8d84-dcc428a08e20@gmail.com>
Date: Sat, 30 Aug 2025 13:00:56 +0800
From: Asuna Yang <spriteovo@...il.com>
To: Conor Dooley <conor@...nel.org>, Jason Montleon <jmontleo@...hat.com>,
Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <lossin@...nel.org>, Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
Danilo Krummrich <dakr@...nel.org>, Paul Walmsley
<paul.walmsley@...ive.com>, Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>, Alexandre Ghiti <alex@...ti.fr>
Cc: rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-riscv@...ts.infradead.org, Asuna Yang <SpriteOvO@...il.com>
Subject: RISC-V: Re-enable GCC+Rust builds
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.
Powered by blists - more mailing lists