[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALNs47sgdi4PU8YXxozMm4=7aQ9RspJsKkKrYuT++9KiC8E-KQ@mail.gmail.com>
Date: Sun, 29 Sep 2024 17:00:29 -0400
From: Trevor Gross <tmgross@...ch.edu>
To: Gary Guo <gary@...yguo.net>
Cc: Miguel Ojeda <ojeda@...nel.org>, Alex Gaynor <alex.gaynor@...il.com>,
Wedson Almeida Filho <wedsonaf@...il.com>, Boqun Feng <boqun.feng@...il.com>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>, Andreas Hindborg <a.hindborg@...sung.com>,
Alice Ryhl <aliceryhl@...gle.com>, Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>, Bill Wendling <morbo@...gle.com>,
Justin Stitt <justinstitt@...gle.com>, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org, llvm@...ts.linux.dev
Subject: Re: [PATCH 1/5] rust: fix size_t in bindgen prototypes of C builtins
On Fri, Sep 13, 2024 at 5:32 PM Gary Guo <gary@...yguo.net> wrote:
> -bindgen_c_flags_final = $(bindgen_c_flags_lto) -D__BINDGEN__
> +# `-fno-builtin` is passed to avoid bindgen from using clang builtin prototypes
> +# for functions like `memcpy` -- if this flag is not passed, bindgen-generated
> +# prototypes use `c_ulong` or `c_uint` depending on architecture instead of
> +# generating `usize`.
> +bindgen_c_flags_final = $(bindgen_c_flags_lto) -fno-builtin -D__BINDGEN__
I wonder how reliable this behavior is. Maybe bindgen could do a
better job controlling this, is there an open issue?
- Trevor
Powered by blists - more mailing lists