mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Thomas Huth <thuth@redhat.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Nathan Chancellor <nathan@kernel.org>,
	 Nicolas Schier <nsc@kernel.org>,
	"Maciej W. Rozycki" <macro@orcam.me.uk>,
	 Nick Huang <sef1548@gmail.com>,
	linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] scripts: headers_install.sh: Normalize __ASSEMBLY__ to __ASSEMBLER__
Date: Thu, 16 Jul 2026 18:40:53 +0200	[thread overview]
Message-ID: <5e05be8c-e9b7-4da7-a182-eefc5043cd2e@t-8ch.de> (raw)
In-Reply-To: <823e3bf3-ef3d-47cf-aff8-1668875a2f38@redhat.com>

Hi Thomas,

On 2026-07-16 12:24:07+0200, Thomas Huth wrote:
> On 09/03/2026 16.58, Thomas Weißschuh wrote:
> > There is an ongoing effort to replace the usage of __ASSEMBLER__ with
> > __ASSEMBLY__ throughout the kernel tree, see for example
> > commit 287d163322b7 ("arm64: Replace __ASSEMBLY__ with __ASSEMBLER__ in
> > non-uapi headers"). The latter is automatically provided by all compilers
> > and preprocessors supported by the kernel, so the explicit definitions
> > of __ASSEMBLER__ can be removed.
> > 
> > However the UAPI headers might be used with older (< GCC 3.0) or
> > non-GCC-compatible compilers, which do not define __ASSEMBLY__
> > automatically.
> 
> I just had a try with gcc 2.95.4 from a Debian Woody installation, and it
> defines __ASSEMBLER__ automatically when compiling *.S files, i.e. gcc 2.95
> does not seem to be a problem. So can you point me to a real case where
> someone tried to use a user space compiler where __ASSEMBLER__ was not
> defined automatically? Otherwise, I think this patch could be reverted
> again.

I don't have a specific case I can point you to. My goal was
consistency. Therefore I am against reverting the patch as long as
both __ASSEMBLER__ and __ASSEMBLY__ are used in the UAPI headers.
If we want to switch to __ASSEMBLER__ for the UAPI headers today,
we should instead invert the logic of this patch to consistently use it
everywhere. After all UAPI headers are migrated, the normalization can
then be removed.


Thomas

> > So this migration may brake users.
> > Also during the migration phase, the UAPI headers will use a mix of
> > *both* __ASSEMBLY__ and __ASSEMBLER__ at the same time, which is ugly.
> > 
> > For now make sure that the exported UAPI headers consistently use
> > __ASSEMBLER__ as before.
> > 
> > Link: https://lore.kernel.org/lkml/164baf81-2824-4943-bbc1-4ae8a160c0cc@t-8ch.de/
> > Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> > ---
> > This should go either through kbuild or asm-generic, I think.
> > ---
> >   scripts/headers_install.sh | 1 +
> >   1 file changed, 1 insertion(+)
> > 
> > diff --git a/scripts/headers_install.sh b/scripts/headers_install.sh
> > index 9c15e748761c..2f1d1767ca26 100755
> > --- a/scripts/headers_install.sh
> > +++ b/scripts/headers_install.sh
> > @@ -36,6 +36,7 @@ sed -E -e '
> >   	s/(^|[^a-zA-Z0-9])__packed([^a-zA-Z0-9_]|$)/\1__attribute__((packed))\2/g
> >   	s/(^|[[:space:](])(inline|asm|volatile)([[:space:](]|$)/\1__\2__\3/g
> >   	s@#(ifndef|define|endif[[:space:]]*/[*])[[:space:]]*_UAPI@#\1 @
> > +	s/__ASSEMBLY__/__ASSEMBLER__/g
> >   ' $INFILE > $TMPFILE || exit 1
> >   scripts/unifdef -U__KERNEL__ -D__EXPORTED_HEADERS__ $TMPFILE > $OUTFILE
> 

  reply	other threads:[~2026-07-16 16:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 15:58 Thomas Weißschuh
2026-03-13 23:56 ` Nathan Chancellor
2026-03-24 17:05   ` Thomas Weißschuh
2026-03-24 18:35     ` Nathan Chancellor
2026-03-24 19:58       ` Thomas Weißschuh
2026-06-13 10:13         ` Nicolas Schier
2026-06-13 16:57           ` Nathan Chancellor
2026-07-16 10:24 ` Thomas Huth
2026-07-16 16:40   ` Thomas Weißschuh [this message]
2026-07-16 18:16     ` Maciej W. Rozycki
2026-07-17 15:25       ` Thomas Weißschuh
2026-07-16 18:52     ` Thomas Huth
2026-07-17 15:28       ` Thomas Weißschuh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5e05be8c-e9b7-4da7-a182-eefc5043cd2e@t-8ch.de \
    --to=linux@weissschuh.net \
    --cc=arnd@arndb.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=nathan@kernel.org \
    --cc=nsc@kernel.org \
    --cc=sef1548@gmail.com \
    --cc=thuth@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome