Conversation
This was referenced Sep 16, 2026
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.
Series: base #1084, wheel #1085, other #1082.
This is the
basepart of a three-category C/Rust/Common Lisp comparison. It preserves odd-candidate scanning and source-level individual marking, following the accepted dense/sparse approach in Rust solution 1.Adds C solution 6 and Common Lisp solution 4. Constant address carries remove sparse-loop indexing work; the Lisp dense generator uses single-assignment bindings so stock SBCL can fold the individual bit operations. Both entries allocate fresh state for every pass. Rust solution 1 is retained unchanged because the attempted changes did not establish a stable gain.
These separate entries keep the direct C kernels independent of the existing C tuning infrastructure and isolate the native-memory, SBCL 2.6.8 implementation from the existing Lisp runtime requirements. The series reserves Lisp 3 for the existing
otherPR and Lisp 5 forwheel.On one logical CPU of an AMD EPYC 9V74, four five-second samples at limit 1,000,000 gave these medians:
The C/Rust gap is small relative to the observed spread. Commands, raw measurements and limits are included.
Native validation passed: independent full-flag checks, memory guards, 10M counts, and ASan/UBSan for C (leak detection unavailable under container tracing). Dockerfiles are included but Docker was unavailable locally. Submitted as a draft pending container/CI review. Development and source inspirations are credited in the READMEs.