Skip to content

Remove BLAKE3 NEON single-block compress path - #30

Merged
Coralesoft merged 2 commits into
mainfrom
fix/blake3-remove-broken-neon-compress
May 15, 2026
Merged

Remove BLAKE3 NEON single-block compress path#30
Coralesoft merged 2 commits into
mainfrom
fix/blake3-remove-broken-neon-compress

Conversation

@Coralesoft

Copy link
Copy Markdown
Collaborator

Summary

BLAKE3_Compress_NEON is a fork-local single-block NEON path. The BLAKE3 reference uses the portable path for this case.

When ValidateBLAKE3() was added to the default cryptest v run, macOS aarch64 CI exposed failures against the official BLAKE3 KATs. This PR removes that NEON-specific path and re-adds the validation coverage.

Changes:

  • remove the NEON dispatch from BLAKE3::Compress
  • delete the NEON helper block from blake3_simd.cpp
  • let aarch64 builds use the portable compress_internal path
  • add ValidateBLAKE3() to ValidateAll()

Verification

Host build passes cleanly.

cryptest v 88 passes the BLAKE3 KATs on the SSE4.1 path.

cryptest v now includes BLAKE3 validation and passes.

macOS Apple Silicon CI covers the aarch64 portable fallback.

Refs: #27

BLAKE3_Compress_NEON provides a fork-local single-block NEON compress path. The BLAKE3 reference uses the portable path for this case.

ValidateBLAKE3 exposed failures against the official BLAKE3 KATs on macOS aarch64 runners. The same tests pass on the x86 SSE4.1 path, so remove the NEON-specific dispatch.

aarch64 builds now use the portable `compress_internal` path from `BLAKE3::Compress`.
`ValidateBLAKE3()` can be run via `cryptest v 88`, but is not included in `ValidateAll()`. The default `cryptest v` run used by CI therefore misses the BLAKE3 KATs.

Add it after the BLAKE2b validation so BLAKE3 runs with the other hash tests.
@Coralesoft Coralesoft self-assigned this May 15, 2026
@Coralesoft
Coralesoft merged commit 1649716 into main May 15, 2026
41 checks passed
@Coralesoft
Coralesoft deleted the fix/blake3-remove-broken-neon-compress branch May 15, 2026 01:26
@Coralesoft Coralesoft mentioned this pull request May 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant