Repository navigation
README: note on the Skylake JCC erratum build flag - #50
Merged
Merged
Conversation
* Organize testing and bench-marking a bit more, it was conflating with optimizations
Open
16 of 22 tasks
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
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.
Part of #31. This adds a Chip-specific optimizations subsection under Building and splits the testing, parity, benchmarking and CI notes into their own subsection.
Background, measured on the cluster nodes with an A/B build at the same commit:
-C llvm-args=-x86-branches-within-32B-boundariesmade the affected cases 7–17% faster (edit, indel, gap-linear, X-drop/Z-drop, banded edit), back to their pre-Remove the AVX2 gather extend kernels (x86 stalls); race-safe bench runs #48 times. Gap-affine was 4% slower. Output was identical.The flag isn't set in
.cargo/config.toml, because it would slow down other CPUs and wouldn't reach downstream crates anyway. The README documents it as an opt-in for Skylake-family Intel CPUs.Docs only, no code changes.
🤖 Generated with Claude Code