[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9de3673c-3b1c-4838-a5fe-e8877a1c3ace@gmail.com>
Date: Thu, 4 Sep 2025 02:52:24 +0800
From: Asuna <spriteovo@...il.com>
To: Conor Dooley <conor@...nel.org>
Cc: 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>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org
Subject: Re: RISC-V: Re-enable GCC+Rust builds
(I apologize if anyone gets this email twice, the first time I
mistakenly sent it as HTML and it was rejected by mailing lists)
> Similarly, something like -Wno-unterminated-string-initialization could
> cause a problem if gcc supports it but not libclang.
And the -Wno-unterminated-string-initialization is not supposed to be a
problem either, today I noticed that in rust/Makefile there is:
# All warnings are inhibited since GCC builds are very experimental,
# many GCC warnings are not supported by Clang, they may only appear in
# some configurations, with new GCC versions, etc.
bindgen_extra_c_flags = -w --target=$(BINDGEN_TARGET)
The -w flag inhibits all warnings, even though Clang may not recognize
it. I was not able to reproduce any errors related to this.
I have a patch ready and will send it later. Please let me know if I'm
missing something there. Thanks.
Powered by blists - more mailing lists