diff options
| author | jsing <> | 2025-05-24 07:07:18 +0000 |
|---|---|---|
| committer | jsing <> | 2025-05-24 07:07:18 +0000 |
| commit | 3cfae66703ed572e7cf2f91e206ec0193019c094 (patch) | |
| tree | 236cfffcebf0e6f3642a69eda1a0bf667229950e /src/lib/libc/stdlib | |
| parent | 0f302b0e0b33ce6709a2f0a3273bfd51b6e76309 (diff) | |
| download | openbsd-3cfae66703ed572e7cf2f91e206ec0193019c094.tar.gz openbsd-3cfae66703ed572e7cf2f91e206ec0193019c094.tar.bz2 openbsd-3cfae66703ed572e7cf2f91e206ec0193019c094.zip | |
Disable libcrypto assembly on arm.
The arm CPU capability detection is uses SIGILL and is unsafe to call from
some contexts. Furthermore, this is only useful to detect NEON support,
which is then unused on OpenBSD due to __STRICT_ALIGNMENT. Requiring a
minimum of ARMv7+VFP+NEON is also not unreasonable.
The SHA-1, SHA-256 and SHA-512 (non-NEON) C code performs within ~5% of
the assembly, as does RSA when using the C based Montgomery multiplication.
The C versions of AES and GHASH code are around ~40-50% of the assembly,
howeer if you care about performance you really want to use
Chacha20Poly1305 on this platform.
This will enable further clean up to proceed.
ok joshua@ kinjiro@ tb@
Diffstat (limited to 'src/lib/libc/stdlib')
0 files changed, 0 insertions, 0 deletions