[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72miDK-Z3v46QX9MQTT_raJTz+ja-Qx5j1qBmptHXkhY+A@mail.gmail.com>
Date: Mon, 16 Sep 2024 18:14:29 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Alice Ryhl <aliceryhl@...gle.com>
Cc: a.hindborg@...sung.com, alex.gaynor@...il.com, benno.lossin@...ton.me,
bjorn3_gh@...tonmail.com, boqun.feng@...il.com, gary@...yguo.net,
kees@...nel.org, linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org,
masahiroy@...nel.org, mmaurer@...gle.com, nathan@...nel.org,
nicolas@...sle.eu, ojeda@...nel.org, peterz@...radead.org,
rust-for-linux@...r.kernel.org, samitolvanen@...gle.com, wedsonaf@...il.com
Subject: Re: [PATCH v2b] rust: cfi: add support for CFI_CLANG with Rust
On Mon, Sep 16, 2024 at 4:07 PM Miguel Ojeda
<miguel.ojeda.sandonis@...il.com> wrote:
>
> It is possible to have CALL_PADDING && !FINEIBT, which means one can
> trigger a build error if the compiler is not recent enough. Should we
> test for CALL_PADDING here?
Alice confirmed offline that she agrees, so I just changed the
requirement in `rust-next`.
[ Replaced `!FINEIBT` requirement with `!CALL_PADDING` to prevent
a build error on older Rust compilers. Fixed typo. - Miguel ]
Cheers,
Miguel
Powered by blists - more mailing lists