A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=OPENBSD_7_9_BASE 2026-01-17T16:18:32+00:00 2026-01-17T16:18:32+00:00 jsing 2026-01-17T16:18:32+00:00 urn:sha1:03fc8f9b9ecbb65326348dd8eccc5d22344abefe Make life easier for portable by providing LIBRESSL_USE_.*_ASSEMBLY defines, which enable/disable assembly for a specific algorithm. This means that selected platforms can include the assembly files and specify a define, rather than having to try to patch the crypto_arch.h headers. Discussed with tb@ 2025-06-28T12:51:08+00:00 jsing 2025-06-28T12:51:08+00:00 urn:sha1:8d0be76398371402b3426575c7326b6e08b0e023 Provide an assembly implementation of SHA-1 for aarch64 using the ARM Cryptographic Extension (CE). This results in around a 2x speed up for larger block sizes. ok tb@ 2025-03-12T14:13:41+00:00 jsing 2025-03-12T14:13:41+00:00 urn:sha1:dcd1700591c767d997c903eba3f3953d562bf23a This provides a SHA-512 assembly implementation that makes use of the ARM Cryptographic Extension (CE), which is found on many arm64 CPUs. This gives a performance gain of up to 2.5x on an Apple M2 (dependent on block size). If an aarch64 machine does not have SHA512 support, then we'll fall back to using the existing C implementation. ok kettenis@ tb@ 2025-03-07T14:21:22+00:00 jsing 2025-03-07T14:21:22+00:00 urn:sha1:504b1d708a6f318c44655b84b6f33ec1734e0375 This provides a SHA-256 assembly implementation that makes use of the ARM Cryptographic Extension (CE), which is found on many arm64 CPUs. This gives a performance gain of up to 7.5x on an Apple M2 (dependent on block size). If an aarch64 machine does not have SHA2 support, then we'll fall back to using the existing C implementation. ok kettenis@ tb@ 2024-11-08T13:34:24+00:00 jsing 2024-11-08T13:34:24+00:00 urn:sha1:b0d9dbfb6f43ca4ff7a16ac1cf3b374342111ffa Replace the aarch64 CPU detection code with a version that parses ISAR0, avoiding signal handling and SIGILL. This gets ISAR0 via sysctl(), but this can be adapted to other mechanisms for other platforms (or alternatively the same can be achieved via HWCAP). This now follows the same naming/design as used by amd64 and i386, hence define HAVE_CRYPTO_CPU_CAPS_INIT for aarch64. ok kettenis@ tb@ 2024-03-29T07:24:09+00:00 jsing 2024-03-29T07:24:09+00:00 urn:sha1:720ec2c3adcad1ded38a6104e4ca139b4a62ac19 These files are now built on all platforms. 2024-03-29T06:03:21+00:00 jsing 2024-03-29T06:03:21+00:00 urn:sha1:5d94d0325a5b03c1ba85b2e0d51af503a072cc2a This is now built on all platforms. 2024-03-29T02:33:45+00:00 jsing 2024-03-29T02:33:45+00:00 urn:sha1:56504c1b338a0cf1e2340ecd05ecce2ff1b68680 This is now built on all platforms. 2024-03-28T12:52:58+00:00 jsing 2024-03-28T12:52:58+00:00 urn:sha1:c552d9c2f8ca2375f539c9afe37341126127d0f7 2024-03-28T01:57:00+00:00 jsing 2024-03-28T01:57:00+00:00 urn:sha1:ec21b0ca38803c02b86ff3aa3362fce09f349c32 This is now built on all platforms.