mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2025-01-22 12:00:28 +07:00
0bc81767c5
When the ARM accelerated ChaCha driver is built as part of a configuration
that has kernel mode NEON disabled, we expect the compiler to propagate
the build time constant expression IS_ENABLED(CONFIG_KERNEL_MODE_NEON) in
a way that eliminates all the cross-object references to the actual NEON
routines, which allows the chacha-neon-core.o object to be omitted from
the build entirely.
Unfortunately, this fails to work as expected in some cases, and we may
end up with a build error such as
chacha-glue.c:(.text+0xc0): undefined reference to `chacha_4block_xor_neon'
caused by the fact that chacha_doneon() has not been eliminated from the
object code, even though it will never be called in practice.
Let's fix this by adding some IS_ENABLED(CONFIG_KERNEL_MODE_NEON) tests
that are not strictly needed from a logical point of view, but should
help the compiler infer that the NEON code paths are unreachable in
those cases.
Fixes:
|
||
---|---|---|
.. | ||
.gitignore | ||
aes-ce-core.S | ||
aes-ce-glue.c | ||
aes-cipher-core.S | ||
aes-cipher-glue.c | ||
aes-neonbs-core.S | ||
aes-neonbs-glue.c | ||
chacha-glue.c | ||
chacha-neon-core.S | ||
chacha-scalar-core.S | ||
crc32-ce-core.S | ||
crc32-ce-glue.c | ||
crct10dif-ce-core.S | ||
crct10dif-ce-glue.c | ||
curve25519-core.S | ||
curve25519-glue.c | ||
ghash-ce-core.S | ||
ghash-ce-glue.c | ||
Kconfig | ||
Makefile | ||
nh-neon-core.S | ||
nhpoly1305-neon-glue.c | ||
poly1305-armv4.pl | ||
poly1305-core.S_shipped | ||
poly1305-glue.c | ||
sha1_glue.c | ||
sha1_neon_glue.c | ||
sha1-armv4-large.S | ||
sha1-armv7-neon.S | ||
sha1-ce-core.S | ||
sha1-ce-glue.c | ||
sha1.h | ||
sha2-ce-core.S | ||
sha2-ce-glue.c | ||
sha256_glue.c | ||
sha256_glue.h | ||
sha256_neon_glue.c | ||
sha256-armv4.pl | ||
sha256-core.S_shipped | ||
sha512-armv4.pl | ||
sha512-core.S_shipped | ||
sha512-glue.c | ||
sha512-neon-glue.c | ||
sha512.h |