perf: optimize crypto fallback paths and clean up Android warning#32
Open
trancee wants to merge 8 commits into
Open
perf: optimize crypto fallback paths and clean up Android warning#32trancee wants to merge 8 commits into
trancee wants to merge 8 commits into
Conversation
trancee
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary:\n- Reworked pure X25519 fallback paths for lower allocation churn and trusted clamped-scalar fast-paths\n- Expanded X25519 Wycheproof coverage and refreshed benchmark baselines\n- Removed a redundant Android L2CAP reconnect tautology warning\n\nVerification:\n- :meshlink:jvmTest\n- :meshlink:testAndroidHostTest\n- :meshlink:compileAndroidMain\n- :benchmarks:jvmBenchmark\n\nNotes:\n- JCA/provider-backed X25519 remains the preferred fast path; pure fallback is still compatibility-focused