From: Thomas Huth <thuth@redhat.com>
To: Linus Walleij <linusw@kernel.org>,
Richard Henderson <richard.henderson@linaro.org>,
Matt Turner <mattst88@gmail.com>,
Magnus Lindholm <linmag7@gmail.com>
Cc: linux-alpha@vger.kernel.org, linux-kernel@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] alpha: Use symbol assignment in SYM_END
Date: Fri, 13 Nov 2026 20:55:59 +0100 [thread overview]
Message-ID: <1125f201-ec86-4139-98a0-fef8e8efe6b4@redhat.com> (raw)
In-Reply-To: <20261103-alpha-compile-v1-1-9e93e2260a9f@kernel.org>
Am 03.11.26 um 10:09 schrieb Linus Walleij:
> Alpha uses the .set directive to select assembler options, so the
> symbol assignment emitted by the generic SYM_END macro fails to assemble.
> This breaks COMPILE_TEST builds left and right, e.g.:
>
> Error: junk at end of line, first unrecognized character is `,'
> Error: .size expression for bcm6846_runner_start does not evaluate to a constant
>
> Override SYM_END to use an ordinary symbol assignment for the calculated
> size. Preserve the symbol type, size and local size symbol while leaving
> other architectures unchanged.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202611031620.n4ptlpo7-lkp@intel.com/
> Signed-off-by: Linus Walleij <linusw@kernel.org>
> ---
> The generic SYM_END uses .set for symbol assignment, but Alpha interprets
> .set as an assembler mode directive. Provide an Alpha override using
> ordinary assignment.
>
> Tested the unchanged Runner wrapper with an Alpha-targeted GNU assembler
> 2.46.1: the original header reproduces the reported errors, while the
> fixed header assembles without warnings. Symbol sizes and the embedded
> Runner bytes were checked. A full Alpha allyesconfig build was not run.
>
> This patch was prepared with LLM assistance.
> ---
> arch/alpha/include/asm/linkage.h | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/arch/alpha/include/asm/linkage.h b/arch/alpha/include/asm/linkage.h
> index aa8661fa60dc..a3f0302c92d0 100644
> --- a/arch/alpha/include/asm/linkage.h
> +++ b/arch/alpha/include/asm/linkage.h
> @@ -6,4 +6,12 @@
> #define SYSCALL_ALIAS(alias, name) \
> asm ( #alias " = " #name "\n\t.globl " #alias)
>
> +#ifdef __ASSEMBLY__
I'm currently trying to convert all __ASSEMBLY__ statements into __ASSEMBLER__:
https://lore.kernel.org/all/20261023064908.66707-1-thuth@redhat.com/
Could you please use __ASSEMBLER__ here, too?
Thanks,
Thomas
> +/* Alpha uses .set for assembler options, not symbol assignments. */
> +#define SYM_END(name, sym_type) \
> + .type name sym_type ASM_NL \
> + .L__sym_size_##name = . - name ASM_NL \
> + .size name, .L__sym_size_##name
> +#endif
> +
> #endif
>
> ---
> base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
> change-id: 20261103-alpha-compile-efdde587115c
>
> Best regards,
> --
> Linus Walleij <linusw@kernel.org>
prev parent reply other threads:[~2026-11-13 19:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 9:09 Linus Walleij
2026-11-03 11:06 ` Magnus Lindholm
2026-11-04 11:51 ` Linus Walleij
2026-11-04 5:51 ` Maciej W. Rozycki
2026-11-13 19:55 ` Thomas Huth [this message]
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=1125f201-ec86-4139-98a0-fef8e8efe6b4@redhat.com \
--to=thuth@redhat.com \
--cc=arnd@arndb.de \
--cc=linmag7@gmail.com \
--cc=linusw@kernel.org \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mattst88@gmail.com \
--cc=richard.henderson@linaro.org \
/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
all inboxes | Powered by JetHome®