[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72n+LbwG=r=zGrEA4-sCD8spJfHF6J7ER=RtaUhFq+ZN3Q@mail.gmail.com>
Date: Thu, 6 Feb 2025 19:58:55 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Kees Cook <kees@...nel.org>
Cc: "Justin M. Forbes" <jforbes@...oraproject.org>, 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 <benno.lossin@...ton.me>, Andreas Hindborg <a.hindborg@...nel.org>,
Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Add -fzero-init-padding-bits to bindgen_skip_cflags
On Thu, Feb 6, 2025 at 7:48 PM Kees Cook <kees@...nel.org> wrote:
>
> Many subsystems base their trees on -rc2, so if it missed rc2, Rust builds
> in a given subsystem will be broken under gcc 15 (but fine in -next).
> But perhaps that's enough of a corner case that it doesn't matter? I
> have other fixes I'm sending to Linus tomorrow, if you'd rather it go in
> sooner? I'm fine either way. :)
Ah, I see.
The Rust-enabled-mixed-GCC/Clang builds are best-effort at the moment
(this should not affect the normal Clang ones) and GCC 15 is still at
least a couple months away as far as I understand, right?
In any case, I can send what I have for -rc2, since I think I will
have others for -rc3 anyway.
Cheers,
Miguel
Powered by blists - more mailing lists