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:06:36 +0200 [thread overview]
Message-ID: <CANiq72kv4DwGLSGTwXYh3-b9h08Erd2RH7wXvVAUAEx2x+q_BA@mail.gmail.com> (raw)
In-Reply-To: <20230815065346.131387-1-andrea.righi@canonical.com>
On Tue, Aug 15, 2023 at 8:54 AM Andrea Righi <andrea.righi@canonical.com> wrote:
>
> Commit df8fc4e934c1 ("kbuild: Enable -fstrict-flex-arrays=3") enabled
> '-fstrict-flex-arrays=3' globally, but bindgen does not recognized this
It may be more accurate to say libclang here (bindgen forwards the options).
Also, df8fc4e934c1 did it so only conditionally (if the C compiler
supports it). This explains what you are seeing: if I am right, you
are compiling with a modern enough GCC, which enables the option, but
with an old enough Clang.
> compiler option, triggering the following build error:
>
> error: unknown argument: '-fstrict-flex-arrays=3', err: true
This should only be true with libclang < 16, since Clang 16
implemented the option, right?
In fact, Clang 15 seems to work too -- it seems the compiler does not
error if the option is not within [0,3] (unlike GCC).
Kees: this should only affect `__builtin_object_size` and not `sizeof`, right?
From a quick test across Clang 14/15/16 and different levels for the
flag (0/1/2/3/4 and no flag), bindgen seems to generate the same
output in all cases: `__IncompleteArrayField` is always generated for
`[]` and `[0]`; and never for `[1]`, i.e. regardless of the flag. The
`sizeof`s agree with the C side, and they are all the same (as
expected because this only changes BOS).
So I think the patch contents (i.e. ignoring the flag for bindgen)
should be fine. Except we could have somewhere a
`__builtin_object_size` influencing a layout. Since GCC seems to
always treat it as not a constexpr (unlike Clang), I assume nobody is
using it like that (since we compile the kernel with and without the
flag). But it is still possible in theory -- it would require
something like:
struct X {
int x[__is_constexpr(__builtin_object_size(s->c, 1)) ? 1 : 2];
};
to make GCC and Clang (as well as Clang `=3` vs. Clang without the
flag) to compile but disagree on the size:
https://godbolt.org/z/6TqPjGK3d
Cheers,
Miguel
next prev parent reply other threads:[~2023-08-15 12:06 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 [this message]
2023-08-15 12:10 ` Miguel Ojeda
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=CANiq72kv4DwGLSGTwXYh3-b9h08Erd2RH7wXvVAUAEx2x+q_BA@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).