diff options
| author | Ard Biesheuvel <ard.biesheuvel@linaro.org> | 2019-10-11 11:08:00 +0200 |
|---|---|---|
| committer | Herbert Xu <herbert@gondor.apana.org.au> | 2019-10-23 19:46:56 +1100 |
| commit | b4d0c0aad57ac3bd1b5141bac5ab1ab1d5e442b3 (patch) | |
| tree | ad70ab4bf9064808d352f8f5fb46a45ec7c0ba83 /arch/arm/crypto/sha1-ce-core.S | |
| parent | 4549f7e5aa27ffc2cba63b5db8842a3b486f5688 (diff) | |
crypto: arm - use Kconfig based compiler checks for crypto opcodes
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>
Diffstat (limited to 'arch/arm/crypto/sha1-ce-core.S')
| -rw-r--r-- | arch/arm/crypto/sha1-ce-core.S | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/arm/crypto/sha1-ce-core.S b/arch/arm/crypto/sha1-ce-core.S index 49a74a441aec..8a702e051738 100644 --- a/arch/arm/crypto/sha1-ce-core.S +++ b/arch/arm/crypto/sha1-ce-core.S @@ -10,6 +10,7 @@ #include <asm/assembler.h> .text + .arch armv8-a .fpu crypto-neon-fp-armv8 k0 .req q0 |