Repository navigation
Conversation
The vectorized BLAKE-2 implementations were only enabled on some x86-64 platforms and caused build failures on many others. `_blake2` and `_hmac` now always use the portable HACL* implementations. The SIMD sources are no longer vendored; their headers are kept since `Hacl_Streaming_HMAC.c` includes them unconditionally.
Documentation build overview
|
|
!buildbot FIPS |
|
🤖 New build scheduled with the buildbot fleet by @picnixz for commit b42ec65 🤖 Results will be shown at: https://buildbot.python.org/all/#/grid?branch=refs%2Fpull%2F160392%2Fmerge The command will test the builders whose names match following regular expression: The builders matched are:
|
|
Currently, benchmarks on a non-emulated Linux (but still using WSL) shows that SIMD doesn't give any real difference (+-10% boost depending on the size of the buffer). I believe that the SIMD performance boost only comes when you use tree hashing. But the latter is hardly used and users should really rely on BLAKE3 instead (please). I will confirm those numbers later but for now I think I'm going to remove the SIMD support. It made much more sense (and was much more easier to maintain) when we had our own sources but with vendored sources, it's a bit more tricky. |
The vectorized BLAKE-2 implementations were only enabled on some x86-64 platforms and caused build failures on many others.
_blake2and_hmacnow always use the portable HACL* implementations.The SIMD sources are no longer vendored; their headers are kept since
Hacl_Streaming_HMAC.cincludes them unconditionally.I haven't run benchmarks yet because I don't have access to a Linux machine with AVX support. But here is what I would expect those interested to do: