Re: include/linux/build_bug.h:78:41: error: static assertion failed: "sizeof(struct rtw8814a_efuse) == 512"

David Laight
2026-04-13T17:02:49Z

On Mon, 13 Apr 2026 15:46:50 +0200
"Arnd Bergmann" <arnd@arndb.de> wrote:

> On Mon, Apr 13, 2026, at 15:01, David Laight wrote:
> > On Mon, 13 Apr 2026 11:30:25 +0200 "Arnd Bergmann" <arnd@arndb.de> wrote:
> >> On Mon, Apr 13, 2026, at 11:15, Geert Uytterhoeven wrote:
> >>
> >> Annotating the union as '__packed' is the correct fix for
> >> the theoretical users of OABI, and does nothing on other
> >> supported targets in Linux.
> >
> > The other option is to ensure the specific drivers aren't ever compiled
> > for !CONFIG_AEABI.
> > Then it'll all get tidied up when you remove it.
>
> That sounds like even more work, for my own testing I have
> just stopped building OABI configuration altogether, though
> I'm still testing ARMv4 kernels.

Is it possible to stop the build robot doing that as well?
Might stop us having to worry about obscure build failures
on something that is heading to its death bed.

>
> > I read that the patches to remove 486 support have been merged.
> > I'm sure it would have made sense to drop everything before P-Pro
> > so that cmov can be used.
>
> That is an entirely unrelated discussion of course. I don't
> think there is any need to discontinue support for 586-class
> processors (Pentium, Pentium MMX, MediaGX/GeodeGX1, AMD K6,
> Vortex86/DX/MX, Via C3) any earlier than the rest of the
> x86-32 kernel support: There is no practical difference
> other than compiler flags, and the Vortex86MX+ is still
> in production (originally released in 2010 with a projected
> 10 year support life). This is very different from earlier
> 486-class CPUs that lack CMPXCHG8B and TSC.

That is a lot more recent that the 1995 date of the P6/pro itself.

I was contemplating writing the 'masked user access' code for x86.
Mostly just involves generating the address space gap.
But the asm is easiest if it uses cmov.
I may need to work out how to use qemu, a userpace consisting of
a busybox shell running as pid 1 is probably enough.

David

>
> Arnd