Re: [linux-next:master 4752/13171] error[E0609]: no field `__bindgen_anon_1` on type `bindings::kernel_param`

[Philip Li <philip.li@intel.com>]

On Thu, Dec 04, 2025 at 12:59:02PM +0100, Daniel Gomez wrote:
> > While we could see from the config that you were using bindgen 0.72.0,
> > it was not clear to us where you get this bindgen from. Obtaining
> > bindgen does not seem to be part of the reproducer instructions (or
> > maybe I am not looking in the right place?).
> > 
> > If I understand correctly, this issue manifested only when building
> > bindgen 0.72.0 with clang-22-git. Building this was next on our list in
> > trying to reproduce, but getting to that conclusion took a while.
> > 
> > Anyway, I want to ask if you can include directions for obtaining or
> > building bindgen in your reproducer instructions?
> 
> + Any reason to use an unreleased clang version for this reports? Since clang-22
> is not officially released yet, issues seen with it seem lower priority than
> those reproduced with stable, released versions. Does it make sense to act
> on these kind of "bleeding edge" reports, or should we wait until they're
> confirmed on a stable release? Does 0day test both?

Hi Andreas, currently the bot will test multiple versions of clang including released
ones like clang-20/clang-21, plus the latest clang from its repo.

We do have some patterns to send reports of low confidence to llvm@lists only or to
have manual check before sending out, probably we can also add some guard when rust
issue is reported on unreleased clang?

> 
> > 
> > Best regards,
> > Andreas Hindborg
> > 
>