Repository navigation
[codex] Add v0.6 general-shape plan API - #5
Merged
Merged
Conversation
TruNcat3
marked this pull request as ready for review
August 11, 2026 06:09
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.
What changed
Why
The project architecture treats shape lowering, space-time mapping, physical processing units, and boundary residence as separate design choices. This change extends that model beyond native power-of-two physical plans while preserving explicit semantics and auditable selection.
User and research impact
Applications can use a professional plan workflow for exact, embedded, and rank-two workloads. The selected
32767 -> 32768, batch-256 FWHT composition falls from 0.73772 ms initially to 0.11759 ms after physical-core and boundary selection. Direct exact FFT intentionally abstains to cuFFT at parity rather than presenting Bluestein overhead as the library result.Structured fused input remains a correct generated candidate but is not enabled by default because it regresses on V100. Cross-GPU transfer and universal superiority remain outside the claim.
Validation
ctest --output-on-failure: 49/49 passed on V100 with CUDA 11.8python3 scripts/check_repository.pygit diff --checkresults/general_shape_fused_input_v100_raw.csv