From: Catalin Marinas <catalin.marinas@arm.com>
To: ndesaulniers@google.com
Cc: will.deacon@arm.com, ard.biesheuvel@linaro.org, arnd@arndb.de,
broonie@kernel.org, linux@armlinux.org.uk,
linux-arm-kernel@lists.infradead.org,
Nathan Chancellor <natechancellor@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lib/raid6: use vdupq_n_u8 to avoid endianness warnings
Date: Thu, 28 Feb 2019 17:47:28 +0000 [thread overview]
Message-ID: <20190228174728.GE226495@arrakis.emea.arm.com> (raw)
In-Reply-To: <20190226040345.202047-1-ndesaulniers@google.com>
On Mon, Feb 25, 2019 at 08:03:42PM -0800, ndesaulniers@google.com wrote:
> Clang warns: vector initializers are not compatible with NEON intrinsics
> in big endian mode [-Wnonportable-vector-initialization]
>
> While this is usually the case, it's not an issue for this case since
> we're initializing the uint8x16_t (16x uint8_t's) with the same value.
>
> Instead, use vdupq_n_u8 which both compilers lower into a single movi
> instruction: https://godbolt.org/z/vBrgzt
>
> This avoids the static storage for a constant value.
>
> Link: https://github.com/ClangBuiltLinux/linux/issues/214
> Suggested-by: Nathan Chancellor <natechancellor@gmail.com>
> Signed-off-by: Nick Desaulniers <ndesaulniers@google.com>
> ---
> lib/raid6/neon.uc | 5 ++---
> lib/raid6/recov_neon_inner.c | 7 ++-----
> 2 files changed, 4 insertions(+), 8 deletions(-)
Queued for 5.1. Thanks.
--
Catalin
prev parent reply other threads:[~2019-02-28 17:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 4:03 ndesaulniers
2019-02-26 7:19 ` Ard Biesheuvel
2019-02-26 20:44 ` Nick Desaulniers
2019-02-26 20:52 ` Ard Biesheuvel
2019-02-28 18:00 ` Robin Murphy
2019-02-28 18:51 ` Nick Desaulniers
2019-02-28 17:47 ` Catalin Marinas [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=20190228174728.GE226495@arrakis.emea.arm.com \
--to=catalin.marinas@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=will.deacon@arm.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
all inboxes | Powered by JetHome®