[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72=KdF2zrcHJEH+YGv9Mn6szsHrZpEWb_y2QkFzButm3Ag@mail.gmail.com>
Date: Thu, 26 Sep 2024 17:40:19 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Conor Dooley <conor@...nel.org>
Cc: Gary Guo <gary@...yguo.net>, Jason Montleon <jmontleo@...hat.com>, ojeda@...nel.org,
alex.gaynor@...il.com, boqun.feng@...il.com, bjorn3_gh@...tonmail.com,
benno.lossin@...ton.me, a.hindborg@...nel.org, aliceryhl@...gle.com,
paul.walmsley@...ive.com, palmer@...belt.com, aou@...s.berkeley.edu,
nathan@...nel.org, ndesaulniers@...gle.com, morbo@...gle.com,
justinstitt@...gle.com, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org,
llvm@...ts.linux.dev, stable@...r.kernel.org
Subject: Re: [PATCH] RISC-V: Fix building rust when using GCC toolchain
On Tue, Sep 17, 2024 at 5:26 PM Conor Dooley <conor@...nel.org> wrote:
>
> Yes, but unfortunately I already knew how it worked. It's not flags I am worried about, it is extensions.
> Even using a libclang that doesn't match clang could be a problem, but we can at least declare that unsupported.
> Not digging it out on an airport bus, but we discussed the lack of GCC support on the original patch adding riscv, and decided against it.
Do you mean you would prefer to avoid supporting the mixed GCC-Clang
builds? If so, do you mean you would prefer to not pick the patch,
i.e. avoid supporting this at all? (If so, then perhaps it would be a
good idea to add a comment there and perhaps a note to
https://docs.kernel.org/rust/arch-support.html).
Otherwise, please let me know if I am misunderstanding -- thanks!
Cheers,
Miguel
Powered by blists - more mailing lists