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

[耀德 黃]

 Tue, Mar 10, 2026 at 02:12:22PM +0000, Maciej W. Rozycki wrote:
> 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
Hi Maciej

Actually, I've learned a lot too. I'd like to ask you again about where in gcc 
`@assembler-with-cpp` is the description of `-D__ASSEMBLER__`? Could you 
provide a website link so I can understand it better? Thank you.

   Nick