From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Nathan Chancellor <nathan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 5.4 only v2] powerpc: boot: Remove leading zero in label in udelay()
Date: Thu, 4 Sep 2025 10:16:33 +0200 [thread overview]
Message-ID: <97fc7eed-c67e-4b5e-90bb-93eb8dd058d7@csgroup.eu> (raw)
In-Reply-To: <20250903211158.2844032-1-nathan@kernel.org>
Le 03/09/2025 à 23:11, Nathan Chancellor a écrit :
> When building powerpc configurations in linux-5.4.y with binutils 2.43
> or newer, there is an assembler error in arch/powerpc/boot/util.S:
>
> arch/powerpc/boot/util.S: Assembler messages:
> arch/powerpc/boot/util.S:44: Error: junk at end of line, first unrecognized character is `0'
> arch/powerpc/boot/util.S:49: Error: syntax error; found `b', expected `,'
> arch/powerpc/boot/util.S:49: Error: junk at end of line: `b'
>
> binutils 2.43 contains stricter parsing of certain labels [1], namely
> that leading zeros are no longer allowed. The GNU assembler
> documentation already somewhat forbade this construct:
>
> To define a local label, write a label of the form 'N:' (where N
> represents any non-negative integer).
>
> Eliminate the leading zero in the label to fix the syntax error. This is
> only needed in linux-5.4.y because commit 8b14e1dff067 ("powerpc: Remove
> support for PowerPC 601") removed this code altogether in 5.10.
>
> Link: https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=226749d5a6ff0d5c607d6428d6c81e1e7e7a994b [1]
> Signed-off-by: Nathan Chancellor <nathan@kernel.org>
Reviewed-by: Christophe Leroy <christophe.leroy@csgroup.eu>
> ---
> v1 -> v2:
> - Adjust commit message to make it clearer this construct was already
> incorrect under the existing GNU assembler documentation (Segher)
>
> v1: https://lore.kernel.org/20250902235234.2046667-1-nathan@kernel.org/
> ---
> arch/powerpc/boot/util.S | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/powerpc/boot/util.S b/arch/powerpc/boot/util.S
> index f11f0589a669..5ab2bc864e66 100644
> --- a/arch/powerpc/boot/util.S
> +++ b/arch/powerpc/boot/util.S
> @@ -41,12 +41,12 @@ udelay:
> srwi r4,r4,16
> cmpwi 0,r4,1 /* 601 ? */
> bne .Ludelay_not_601
> -00: li r0,86 /* Instructions / microsecond? */
> +0: li r0,86 /* Instructions / microsecond? */
> mtctr r0
> 10: addi r0,r0,0 /* NOP */
> bdnz 10b
> subic. r3,r3,1
> - bne 00b
> + bne 0b
> blr
>
> .Ludelay_not_601:
>
> base-commit: c25f780e491e4734eb27d65aa58e0909fd78ad9f
next prev parent reply other threads:[~2025-09-04 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 21:11 [PATCH 5.4 only v2] powerpc: boot: Remove leading zero in label in udelay() Nathan Chancellor
2025-09-04 8:16 ` Christophe Leroy [this message]
2025-09-04 16:05 ` Patch "powerpc: boot: Remove leading zero in label in udelay()" has been added to the 5.4-stable tree gregkh
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=97fc7eed-c67e-4b5e-90bb-93eb8dd058d7@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=gregkh@linuxfoundation.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=nathan@kernel.org \
--cc=npiggin@gmail.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).