[Question] Will switching Linux UAPI headers from __ASSEMBLY__ to __ASSEMBLER__ affect glibc?

Maciej W. Rozycki macro@orcam.me.uk
Tue Mar 10 14:12:22 GMT 2026


On Sat, 7 Mar 2026, Nick Huang wrote:

> > >  Only as from GCC commit f8f769ea4e69; don't we care to support older GCC
> > > versions with installed headers anymore?
> >
> > There is only one installed header that uses __ASSEMBLY__,
> > sysdeps/alpha/bits/setjmp.h.  All other installed headers use
> > __ASSEMBLER__ only.
> >
> > --
> > Andreas Schwab, SUSE Labs, schwab@suse.de
> > GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
> > "And now for something completely different."
> 
> Is sysdeps/alpha/bits/setjmp.h really the only remaining header using
> __ASSEMBLY__ while all others have switched to __ASSEMBLER__, even for
> older GCC versions?

 I have now dug a bit deeper and realised that GCC used to have explicit 
-D__ASSEMBLER__ in the specs for `@assembler-with-cpp' before switching to 
the internal macro definition.  So I take my concern back, the change is 
good to go in.  Apologies for the confusion.

  Maciej


More information about the Libc-alpha mailing list