wgsl: clarify compute subgroup_invocation_id's are dense starting at 0 #5520
Conversation
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
Contributor
|
Previews, as seen when this build job started (9a420b6): |
dneto0
commented
Jan 19, 2026
|
|
||
| In a [=compute shader stage|compute=] shader, IDs begin at zero and are dense. | ||
| That is, when the compute shader begins execution, then within each subgroup: | ||
| * One invocation will have `subgroup_invocation_id` = 0, and |
Contributor
Author
There was a problem hiding this comment.
I know this first clause is redundant, but I think it helps readability
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixed: #5519