diff options
| author |   Ard Biesheuvel <ard.biesheuvel@linaro.org> | 2022-06-29 11:02:26 -0700 |
|---|---|---|
| committer |   Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2022-07-02 16:28:52 +0200 |
| commit | 3bf992f9d9a8469e4ded1826d84ed395e836ca43 (patch) | |
| tree | 192a5ca9b7926ead889f6a89607e6b0195ea8f32 /arch/arm/crypto/ghash-ce-core.S | |
| parent | ARM: 9029/1: Make iwmmxt.S support Clang's integrated assembler (diff) | |
| download | wireguard-linux-3bf992f9d9a8469e4ded1826d84ed395e836ca43.tar.xz wireguard-linux-3bf992f9d9a8469e4ded1826d84ed395e836ca43.zip | |
crypto: arm - use Kconfig based compiler checks for crypto opcodes
commit b4d0c0aad57ac3bd1b5141bac5ab1ab1d5e442b3 upstream
Instead of allowing the Crypto Extensions algorithms to be selected when
using a toolchain that does not support them, and complain about it at
build time, use the information we have about the compiler to prevent
them from being selected in the first place. Users that are stuck with
a GCC version <4.8 are unlikely to care about these routines anyway, and
it cleans up the Makefile considerably.
While at it, add explicit 'armv8-a' CPU specifiers to the code that uses
the 'crypto-neon-fp-armv8' FPU specifier so we don't regress Clang, which
will complain about this in version 10 and later.
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch/arm/crypto/ghash-ce-core.S')
| -rw-r--r-- | arch/arm/crypto/ghash-ce-core.S | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/arm/crypto/ghash-ce-core.S b/arch/arm/crypto/ghash-ce-core.S index c47fe81abcb0..534c9647726d 100644 --- a/arch/arm/crypto/ghash-ce-core.S +++ b/arch/arm/crypto/ghash-ce-core.S @@ -88,6 +88,7 @@ T3_H .req d17 .text + .arch armv8-a .fpu crypto-neon-fp-armv8 .macro __pmull_p64, rd, rn, rm, b1, b2, b3, b4 |