wolfssl/wolfcrypt
Tobias Frauenschläger 70d28ef42e armv8: enable the SHA-3 extension the ML-KEM assembly needs
The ARM64 ML-KEM port emits eor3, which is not in the base ARMv8-A a toolchain
may be invoked with, and the file carries no directive:

  armv8-mlkem-asm.S: Error: selected processor does not support
                            `eor3 v31.16b,v0.16b,v5.16b,v10.16b'

The directive sits inside WOLFSSL_ARMASM_CRYPTO_SHA3, the guard selecting the
variant that needs it, so a build that has not opted in never asks for it.

The same file's sqrdmlsh deliberately gets none. RDMA is opt-out
(WOLFSSL_AARCH64_NO_SQRDMLSH) where SHA-3 is opt-in, and on a target with no
way to read the ID registers cpuid.c reports it present whenever that macro is
unset. A directive there would turn a build the assembler correctly rejects
into an image that traps on the first sqrdmlsh, so the mnemonic is left to
answer to -mcpu.
2026-09-17 10:27:11 +02:00
..
benchmark Merge pull request #11399 from night1rider/ecies-dev-id-change 2026-09-15 14:31:49 -06:00
src armv8: enable the SHA-3 extension the ML-KEM assembly needs 2026-09-17 10:27:11 +02:00
test Merge pull request #11399 from night1rider/ecies-dev-id-change 2026-09-15 14:31:49 -06:00