From: Nick Huang <sef1548@gmail.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: linux@armlinux.org.uk, davidgow@google.com,
dongsheng.yang@linux.dev, dory85109@gmail.com,
ebiggers@kernel.org, idryomov@gmail.com, jlayton@kernel.org,
john.g.garry@oracle.com, namhyung@kernel.org, robh@kernel.org,
kusogame68@gmail.com, wdhh6@aliyun.com, wqu@suse.com,
yot4106@gmail.com, likerockman102@hotmail.com,
squid@squidspirit.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm: Replace ASSEMBLY with ASSEMBLER in uapi headers
Date: Tue, 3 Mar 2026 16:10:08 +0000 [thread overview]
Message-ID: <20260303161012.2983-1-sef1548@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2603011816460.44093@angie.orcam.me.uk>
On Sun, 1 Mar 2026, Maciej W. Rozycki wrote:
> It seems to whom? Have you got a reference to a discussion with libc
> maintainers where the consensus has been that support for older compilers
> can be dropped? Why does it remain in the GNU C library?
I have now consulted the glibc maintainers directly on this question.
The thread is available here:
https://inbox.sourceware.org/libc-alpha/mvm342hx8tf.fsf@suse.de/
Andreas Schwab (SUSE Labs) responded:
"Since the compiler will define __ASSEMBLER__ automatically when
preprocessing assembler-with-cpp files, there is no need to change
anything on the glibc side. The places that define __ASSEMBLY__ for
that purpose will just become redundant."
Best regards,
Nick Huang <sef1548@gmail.com>
next prev parent reply other threads:[~2026-03-03 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 12:13 [PATCH v2] arm: Replace ASSEMBLY with ASSEMBLER in uapi headers Nick Huang
2026-02-28 12:19 ` Thomas Weißschuh
2026-02-28 12:45 ` Nick Huang
2026-03-01 20:12 ` Maciej W. Rozycki
2026-03-01 22:06 ` Thomas Weißschuh
2026-03-03 16:10 ` Nick Huang [this message]
2026-03-09 15:24 ` [PATCH v2] arm: Replace ASSEMBLY with ASSEMBLER in uapi Nick Huang
2026-03-09 16:01 ` Thomas Weißschuh
2026-03-10 14:13 ` Maciej W. Rozycki
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=20260303161012.2983-1-sef1548@gmail.com \
--to=sef1548@gmail.com \
--cc=davidgow@google.com \
--cc=dongsheng.yang@linux.dev \
--cc=dory85109@gmail.com \
--cc=ebiggers@kernel.org \
--cc=idryomov@gmail.com \
--cc=jlayton@kernel.org \
--cc=john.g.garry@oracle.com \
--cc=kusogame68@gmail.com \
--cc=likerockman102@hotmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=macro@orcam.me.uk \
--cc=namhyung@kernel.org \
--cc=robh@kernel.org \
--cc=squid@squidspirit.com \
--cc=wdhh6@aliyun.com \
--cc=wqu@suse.com \
--cc=yot4106@gmail.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