From: Russell Currey <ruscur@russell.cc>
To: Alexey Kardashevskiy <aik@ozlabs.ru>, llvm@lists.linux.dev
Cc: Nathan Lynch <nathanl@linux.ibm.com>,
Fabiano Rosas <farosas@linux.ibm.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Nicholas Piggin <npiggin@gmail.com>,
Nathan Chancellor <nathan@kernel.org>,
Joel Stanley <joel@jms.id.au>,
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, Daniel Axtens <dja@axtens.net>
Subject: Re: [PATCH kernel 3/3] powerpc/llvm/lto: Workaround conditional branches in FTR_SECTION_ELSE
Date: Fri, 11 Feb 2022 16:44:04 +1000 [thread overview]
Message-ID: <62e5a57c18557a20db8e60b3995a549cde622cdb.camel@russell.cc> (raw)
In-Reply-To: <20220211023125.1790960-4-aik@ozlabs.ru>
On Fri, 2022-02-11 at 13:31 +1100, Alexey Kardashevskiy wrote:
> diff --git a/arch/powerpc/lib/memcpy_64.S
> b/arch/powerpc/lib/memcpy_64.S
> index 016c91e958d8..286c7e2d0883 100644
> --- a/arch/powerpc/lib/memcpy_64.S
> +++ b/arch/powerpc/lib/memcpy_64.S
> @@ -50,10 +50,11 @@ ALT_FTR_SECTION_END_IFCLR(CPU_FTR_VMX_COPY)
> At the time of writing the only CPU that has this combination of
> bits
> set is Power6. */
> test_feature = (SELFTEST_CASE == 1)
> + beq .ldst_aligned
Hey Alexey, typo here (should be .Ldst_aligned) that breaks the build
for BE.
> BEGIN_FTR_SECTION
> nop
prev parent reply other threads:[~2022-02-11 6:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 2:31 [PATCH kernel 0/3] powerpc/llvm/lto: Enable CONFIG_LTO_CLANG_THIN=y Alexey Kardashevskiy
2022-02-11 2:31 ` [PATCH kernel 1/3] powerpc/64: Allow LLVM LTO builds Alexey Kardashevskiy
2022-02-11 2:31 ` [PATCH kernel 2/3] powerpc/llvm: Sample config for LLVM LTO Alexey Kardashevskiy
2022-02-11 11:44 ` Naveen N. Rao
2022-02-12 0:05 ` Nick Desaulniers
2022-02-16 1:28 ` Alexey Kardashevskiy
2022-02-11 2:31 ` [PATCH kernel 3/3] powerpc/llvm/lto: Workaround conditional branches in FTR_SECTION_ELSE Alexey Kardashevskiy
2022-02-11 6:44 ` Russell Currey [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=62e5a57c18557a20db8e60b3995a549cde622cdb.camel@russell.cc \
--to=ruscur@russell.cc \
--cc=aik@ozlabs.ru \
--cc=dja@axtens.net \
--cc=farosas@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=nathanl@linux.ibm.com \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=ndesaulniers@google.com \
--cc=npiggin@gmail.com \
/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).