linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sasha Levin <sashal@kernel.org>,
	stable@vger.kernel.org, Madhavan Srinivasan <maddy@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Nicholas Piggin <npiggin@gmail.com>,
	Christophe Leroy <christophe.leroy@csgroup.eu>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 5.4 only] powerpc: boot: Remove unnecessary zero in label in udelay()
Date: Wed, 3 Sep 2025 16:19:24 -0500	[thread overview]
Message-ID: <aLiw3L76FR5k-Xen@gate> (raw)
In-Reply-To: <20250903211442.GA2866185@ax162>

Hi!

On Wed, Sep 03, 2025 at 02:14:42PM -0700, Nathan Chancellor wrote:
> On Wed, Sep 03, 2025 at 01:15:38AM -0500, Segher Boessenkool wrote:
> > On Tue, Sep 02, 2025 at 04:52:34PM -0700, Nathan Chancellor wrote:
> > > 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].
> > > 
> > > Remove the unnecessary leading zero to fix the build.
> > 
> > To fix it by getting rid of this syntax error, you mean?  "00" is not a
> > valid label name: a) it cannot be a symbol name, it starts with a digit;
> > and b) it isn't a valid local label either.  As the manual says
> > > To define a local label, write a label of the form ‘N:’ (where N
> > > represents any non-negative integer).
> > "0" is written "0", not as "00" (or "0-0" or even "0-0-0", hehe).
> 
> Sure, I have sent a v2 that hopefully makes it a little clearer that the
> code in the kernel was already problematic under the existing rules.
> 
> https://lore.kernel.org/20250903211158.2844032-1-nathan@kernel.org/

You forgot to cc: me on that :-)  I have it via linuxppc-dev@ of course.

Looks great, thank you!


Segher


      reply	other threads:[~2025-09-03 21:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02 23:52 [PATCH 5.4 only] powerpc: boot: Remove unnecessary zero in label in udelay() Nathan Chancellor
2025-09-03  6:15 ` Segher Boessenkool
2025-09-03 21:14   ` Nathan Chancellor
2025-09-03 21:19     ` Segher Boessenkool [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=aLiw3L76FR5k-Xen@gate \
    --to=segher@kernel.crashing.org \
    --cc=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).