crypto: aegis128 - avoid spurious references crypto_aegis128_update_simd
authorArd Biesheuvel <ardb@kernel.org>
Mon, 30 Nov 2020 12:26:20 +0000 (13:26 +0100)
committerHerbert Xu <herbert@gondor.apana.org.au>
Fri, 4 Dec 2020 07:16:53 +0000 (18:16 +1100)
commit0464e0ef4f144bd5f2fa6ef6e06ab1e0ae4806f6
tree95fed225bbad0a64a0bf550952bc5be65e806c93
parent1069e97688b21b9c754dc8364ccfb3fea79788bf
crypto: aegis128 - avoid spurious references crypto_aegis128_update_simd

Geert reports that builds where CONFIG_CRYPTO_AEGIS128_SIMD is not set
may still emit references to crypto_aegis128_update_simd(), which
cannot be satisfied and therefore break the build. These references
only exist in functions that can be optimized away, but apparently,
the compiler is not always able to prove this.

So add some explicit checks for CONFIG_CRYPTO_AEGIS128_SIMD to help the
compiler figure this out.

Tested-by: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
crypto/aegis128-core.c