[SIMT][OPT] Add persistent SIMT fragment materialization#978
Open
KurrinQu wants to merge 1 commit into
Open
Conversation
Contributor
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
KurrinQu
force-pushed
the
qkl/ptoas-persistent-simt-fragment-design
branch
3 times, most recently
from
July 23, 2026 03:46
32c5c72 to
ac8fe5f
Compare
KurrinQu
force-pushed
the
qkl/ptoas-persistent-simt-fragment-design
branch
from
July 23, 2026 18:28
ac8fe5f to
1948788
Compare
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.
Summary
Add PTOAS support for keeping SIMT fragment values in dedicated register
slots across multiple inline SIMT sections.
The transformation replaces repeated UB-to-register loads with explicit
pto.keep/pto.resumetraffic while preserving the existing VPTO loweringand outlining flow.
Changes
then outline them into
pto.simt_entryhelpers andpto.simt_launchcalls.assignment, vector accesses, control-flow contracts, invalid offsets,
launch-dimension mismatches, and slot-budget violations.