public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: "Pierre-Clément Tosi" <ptosi@google.com>
Cc: u-boot@lists.denx.de, Matthias Weisser <weisserm@arcor.de>
Subject: Re: [PATCH] arm: Fix bad memcpy.S str8w macro argument count
Date: Wed, 10 Nov 2021 09:58:42 -0500	[thread overview]
Message-ID: <20211110145842.GF24579@bill-the-cat> (raw)
In-Reply-To: <20211110145138.5mdo54smpj4xoaru@google.com>

[-- Attachment #1: Type: text/plain, Size: 2253 bytes --]

On Wed, Nov 10, 2021 at 03:51:38PM +0100, Pierre-Clément Tosi wrote:
> On Wed, Nov 10, 2021 at 09:14:14AM -0500, Tom Rini wrote:
> > On Wed, Nov 10, 2021 at 03:04:40PM +0100, Pierre-Clément Tosi wrote:
> > 
> > > Remove the extra (empty) argument passed to str8w, causing the following
> > > error:
> > > 
> > >    <instantiation>:40:47: error: too many positional arguments
> > >      str8w r0, r3, r4, r5, r6, r7, r8, r9, ip, , abort=19f
> > >                                                  ^
> > >    u-boot/arch/arm/lib/memcpy.S:240:5: note: while in macro instantiation
> > >    17: forward_copy_shift pull=16 push=16
> > >        ^
> > > 
> > > Note: no functional change intended.
> > > 
> > > Fixes: d8834a1323af ("arm: Use optimized memcpy and memset from linux")
> > > Signed-off-by: Pierre-Clément Tosi <ptosi@google.com>
> > > ---
> > >  arch/arm/lib/memcpy.S | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/arch/arm/lib/memcpy.S b/arch/arm/lib/memcpy.S
> > > index f7fb77235c..eee7a219ce 100644
> > > --- a/arch/arm/lib/memcpy.S
> > > +++ b/arch/arm/lib/memcpy.S
> > > @@ -210,7 +210,7 @@ ENTRY(memcpy)
> > >  		orr	r9, r9, ip, lspush #\push
> > >  		mov	ip, ip, lspull #\pull
> > >  		orr	ip, ip, lr, lspush #\push
> > > -		str8w	r0, r3, r4, r5, r6, r7, r8, r9, ip, , abort=19f
> > > +		str8w	r0, r3, r4, r5, r6, r7, r8, r9, ip, abort=19f
> > >  		bge	12b
> > >  	PLD(	cmn	r2, #96			)
> > >  	PLD(	bge	13b			)
> > 
> > Since this code is both taken from Linux, and likely in need of a
> > re-sync with Linux, has this issue been addressed upstream?  Or no
> > longer present?  Thanks.
> > 
> > -- 
> > Tom
> 
> In a way, both; it is no longer present in memcpy.S because that file now uses
> the shared implementation from copy_template.S but that particular line was
> fixed in the same way (and funnily enough with a similar commit message) more
> than 2 years ago in baf2df8e15be22b8bd24bdd6fd4575b6641bcfd1 ("ARM: 8827/1: fix
> argument count to match macro definition").
> 
> Therefore, re-syncing would certainly solve the issue.

Any chance you have time / interest in a resync?  Otherwise, I'll take
your patch soon.  Thanks!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2021-11-10 14:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10 14:04 [PATCH] arm: Fix bad memcpy.S str8w macro argument count Pierre-Clément Tosi
2021-11-10 14:14 ` Tom Rini
2021-11-10 14:51   ` Pierre-Clément Tosi
2021-11-10 14:58     ` Tom Rini [this message]
2021-11-16 19:26 ` Tom Rini

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=20211110145842.GF24579@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=ptosi@google.com \
    --cc=u-boot@lists.denx.de \
    --cc=weisserm@arcor.de \
    /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