From: Michael Ellerman <mpe@ellerman.id.au>
To: Mina Almasry <almasrymina@google.com>
Cc: linuxppc-dev@lists.ozlabs.org, christophe.leroy@csgroup.eu,
segher@kernel.crashing.org, sfr@canb.auug.org.au,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
kuba@kernel.org
Subject: Re: [PATCH] powerpc/atomic: Use YZ constraints for DS-form instructions
Date: Tue, 17 Sep 2024 14:35:17 +1000 [thread overview]
Message-ID: <878qvqrj7e.fsf@mail.lhotse> (raw)
In-Reply-To: <CAHS8izM-3DSw+hvFasu=xge5st9cE9MrwJ3FOOHpYHsj5r0Ydg@mail.gmail.com>
Mina Almasry <almasrymina@google.com> writes:
> On Mon, Sep 16, 2024 at 5:05 AM Michael Ellerman <mpe@ellerman.id.au> wrote:
>>
>> The 'ld' and 'std' instructions require a 4-byte aligned displacement
>> because they are DS-form instructions. But the "m" asm constraint
>> doesn't enforce that.
>>
>> That can lead to build errors if the compiler chooses a non-aligned
>> displacement, as seen with GCC 14:
>>
>> /tmp/ccuSzwiR.s: Assembler messages:
>> /tmp/ccuSzwiR.s:2579: Error: operand out of domain (39 is not a multiple of 4)
>> make[5]: *** [scripts/Makefile.build:229: net/core/page_pool.o] Error 1
>>
>> Dumping the generated assembler shows:
>>
>> ld 8,39(8) # MEM[(const struct atomic64_t *)_29].counter, t
>>
>> Use the YZ constraints to tell the compiler either to generate a DS-form
>> displacement, or use an X-form instruction, either of which prevents the
>> build error.
>>
>> See commit 2d43cc701b96 ("powerpc/uaccess: Fix build errors seen with
>> GCC 13/14") for more details on the constraint letters.
>>
>> Fixes: 9f0cbea0d8cc ("[POWERPC] Implement atomic{, 64}_{read, write}() without volatile")
>> Cc: stable@vger.kernel.org # v2.6.24+
>> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
>> Closes: https://lore.kernel.org/all/20240913125302.0a06b4c7@canb.auug.org.au
>> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
>
> I'm not familiar enough with the code around the changes, but I have
> been able to confirm cherry-picking this resolves the build issue I'm
> seeing on net-next, so, FWIW,
>
> Tested-by: Mina Almasry <almasrymina@google.com>
Thanks.
cheers
next prev parent reply other threads:[~2024-09-17 4:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 12:05 [PATCH] powerpc/atomic: Use YZ constraints for DS-form instructions Michael Ellerman
2024-09-16 14:49 ` Mina Almasry
2024-09-17 4:35 ` Michael Ellerman [this message]
2024-09-17 7:37 ` Segher Boessenkool
2024-09-19 12:43 ` Michael Ellerman
2024-09-17 12:22 ` Michael Ellerman
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=878qvqrj7e.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=almasrymina@google.com \
--cc=christophe.leroy@csgroup.eu \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=segher@kernel.crashing.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.