[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72nqTfJJb9oQZGpAn2KZwDXwp6StVKKETWF-m3fLpnsiPQ@mail.gmail.com>
Date: Tue, 15 Aug 2023 14:10:12 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Andrea Righi <andrea.righi@...onical.com>
Cc: Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Wedson Almeida Filho <wedsonaf@...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>,
"Gustavo A . R . Silva" <gustavoars@...nel.org>,
Kees Cook <keescook@...omium.org>,
Masahiro Yamada <masahiroy@...nel.org>,
rust-for-linux@...r.kernel.org, linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org,
Nick Desaulniers <ndesaulniers@...gle.com>,
Nathan Chancellor <nathan@...nel.org>
Subject: Re: [PATCH] rust: fix bindgen build error with fstrict-flex-arrays
On Tue, Aug 15, 2023 at 2:06 PM Miguel Ojeda
<miguel.ojeda.sandonis@...il.com> wrote:
>
> to make GCC and Clang (as well as Clang `=3` vs. Clang without the
> flag) to compile but disagree on the size:
To be clear: Clang `=3` vs. Clang without the flag should not be a
problem for us because under `CC_IS_CLANG` we pass the flags unaltered
to bindgen.
But for GCC-built kernels with Rust enabled, the disagreement above
could be a problem.
Cheers,
Miguel
Powered by blists - more mailing lists