Hi Nathan,
Sorry, with all the other things I ended up not replying to you before
going to sleep.
On Wed, Apr 14, 2021 at 8:59 PM Nathan Chancellor wrote:
>
> Shuffling this around will cause this issue (I never saw you CC'd on the
> thread).
>
>
On Thu, Apr 15, 2021 at 1:47 AM Nick Desaulniers
wrote:
>
> I'm ok with this approach, but I'm curious:
> If the user made a copy of the CLANG_FLAGS variable and modified its
> copy, would TENTATIVE_CLANG_FLAGS even be necessary? IIUC,
> TENTATIVE_CLANG_FLAGS is used to filter out certain flags
On Wed, Apr 14, 2021 at 11:48 AM wrote:
>
> From: Miguel Ojeda
>
> To support Rust under GCC-built kernels, we need to save the flags that
> would have been passed if the kernel was being compiled with Clang.
>
> The reason is that bindgen -- the tool we use to generate Rust bindings
> to the C
Hi Miguel,
On Wed, Apr 14, 2021 at 08:45:54PM +0200, oj...@kernel.org wrote:
> From: Miguel Ojeda
>
> To support Rust under GCC-built kernels, we need to save the flags that
> would have been passed if the kernel was being compiled with Clang.
>
> The reason is that bindgen -- the tool we use
From: Miguel Ojeda
To support Rust under GCC-built kernels, we need to save the flags that
would have been passed if the kernel was being compiled with Clang.
The reason is that bindgen -- the tool we use to generate Rust bindings
to the C side of the kernel -- relies on libclang to parse C.
5 matches
Mail list logo