From: Ard Biesheuvel <ardb@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: herbert@gondor.apana.org.au, Ard Biesheuvel <ardb@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Nathan Chancellor <nathan@kernel.org>
Subject: [PATCH v3 0/2] xor: enable auto-vectorization in Clang
Date: Sat, 5 Feb 2022 08:58:35 +0100 [thread overview]
Message-ID: <20220205075837.153418-1-ardb@kernel.org> (raw)
Update the xor_blocks() prototypes so that the compiler understands that
the inputs always refer to distinct regions of memory. This is implied
by the existing implementations, as they use different granularities for
the load/xor/store loops.
With that, we can fix the ARM/Clang version, which refuses to SIMD
vectorize otherwise, and throws a spurious warning related to the GCC
version being incompatible.
Changes since v2:
- fix arm64 build after rebase
- name PPC argument names consistently
- add Nick's acks and link tags
Changes since v1:
- fix PPC build
- add Nathan's Tested-by
Cc: Nick Desaulniers <ndesaulniers@google.com>
Cc: Nathan Chancellor <nathan@kernel.org>
Ard Biesheuvel (2):
lib/xor: make xor prototypes more friendely to compiler vectorization
crypto: arm/xor - make vectorized C code Clang-friendly
arch/alpha/include/asm/xor.h | 53 ++++++++----
arch/arm/include/asm/xor.h | 42 ++++++----
arch/arm/lib/xor-neon.c | 12 +--
arch/arm64/include/asm/xor.h | 21 +++--
arch/arm64/lib/xor-neon.c | 46 +++++++----
arch/ia64/include/asm/xor.h | 21 +++--
arch/powerpc/include/asm/xor_altivec.h | 25 +++---
arch/powerpc/lib/xor_vmx.c | 28 ++++---
arch/powerpc/lib/xor_vmx.h | 27 ++++---
arch/powerpc/lib/xor_vmx_glue.c | 32 ++++----
arch/s390/lib/xor.c | 21 +++--
arch/sparc/include/asm/xor_32.h | 21 +++--
arch/sparc/include/asm/xor_64.h | 42 ++++++----
arch/x86/include/asm/xor.h | 42 ++++++----
arch/x86/include/asm/xor_32.h | 42 ++++++----
arch/x86/include/asm/xor_avx.h | 21 +++--
include/asm-generic/xor.h | 84 +++++++++++++-------
include/linux/raid/xor.h | 21 +++--
18 files changed, 384 insertions(+), 217 deletions(-)
--
2.30.2
next reply other threads:[~2022-02-05 7:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 7:58 Ard Biesheuvel [this message]
2022-02-05 7:58 ` [PATCH v3 1/2] lib/xor: make xor prototypes more friendely to compiler vectorization Ard Biesheuvel
2022-02-05 8:06 ` Ard Biesheuvel
2022-02-05 7:58 ` [PATCH v3 2/2] crypto: arm/xor - make vectorized C code Clang-friendly Ard Biesheuvel
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=20220205075837.153418-1-ardb@kernel.org \
--to=ardb@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.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 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.