From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Andrea Righi <andrea.righi@canonical.com>
Cc: "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Gustavo A . R . Silva" <gustavoars@kernel.org>,
"Kees Cook" <keescook@chromium.org>,
"Masahiro Yamada" <masahiroy@kernel.org>,
rust-for-linux@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Nathan Chancellor" <nathan@kernel.org>
Subject: Re: [PATCH] rust: fix bindgen build error with fstrict-flex-arrays
Date: Tue, 15 Aug 2023 14:10:12 +0200 [thread overview]
Message-ID: <CANiq72nqTfJJb9oQZGpAn2KZwDXwp6StVKKETWF-m3fLpnsiPQ@mail.gmail.com> (raw)
In-Reply-To: <CANiq72kv4DwGLSGTwXYh3-b9h08Erd2RH7wXvVAUAEx2x+q_BA@mail.gmail.com>
On Tue, Aug 15, 2023 at 2:06 PM Miguel Ojeda
<miguel.ojeda.sandonis@gmail.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
next prev parent reply other threads:[~2023-08-15 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-15 6:53 [PATCH] rust: fix bindgen build error with fstrict-flex-arrays Andrea Righi
2023-08-15 12:06 ` Miguel Ojeda
2023-08-15 12:10 ` Miguel Ojeda [this message]
2023-08-15 12:44 ` Andrea Righi
2023-08-15 12:49 ` Miguel Ojeda
2023-08-17 3:45 ` Kees Cook
2023-09-23 3:43 ` Gary Guo
2023-10-08 19:59 ` Miguel Ojeda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANiq72nqTfJJb9oQZGpAn2KZwDXwp6StVKKETWF-m3fLpnsiPQ@mail.gmail.com \
--to=miguel.ojeda.sandonis@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=andrea.righi@canonical.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=gustavoars@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).