Verify allowReorder reshapes#9905
Merged
Merged
Conversation
lezcano
approved these changes
Apr 2, 2026
ThomasRaoux
reviewed
Apr 2, 2026
neildhar
force-pushed
the
neildhar/pr9905
branch
from
ba1d610 to
6637e51
Compare
neildhar
force-pushed
the
neildhar/pr9905
branch
from
6637e51 to
cbfc9ba
Compare
neildhar
force-pushed
the
neildhar/pr9926
branch
from
3a9768a to
5ceb73f
Compare
neildhar
force-pushed
the
neildhar/pr9905
branch
2 times, most recently
from
2e43721 to
d6d6763
Compare
neildhar
force-pushed
the
neildhar/pr9926
branch
from
5ceb73f to
0b219b4
Compare
neildhar
force-pushed
the
neildhar/pr9905
branch
2 times, most recently
from
733f6c8 to
5650fe9
Compare
ThomasRaoux
approved these changes
Apr 7, 2026
allowReorder reshapes still have a restriction that they cannot imply moving elements between threads and warps. Now that inferring the encoding is guaranteed to produce the given hint encoding if it is valid, we can check this with the existing verification code.
neildhar
force-pushed
the
neildhar/pr9905
branch
from
5650fe9 to
77e44da
Compare
ThomasRaoux
added a commit
to ThomasRaoux/triton
that referenced
this pull request
Apr 9, 2026
This reverts commit 6786088.
neildhar
added a commit
that referenced
this pull request
Apr 10, 2026
allowReorder reshapes still have a restriction that they cannot imply moving elements between threads and warps. Now that inferring the encoding is guaranteed to produce the given hint encoding if it is valid, we can check this with the existing verification code.
This was referenced Apr 10, 2026
neildhar
added a commit
that referenced
this pull request
Apr 10, 2026
Reland of #9905. allowReorder reshapes still have a restriction that they cannot imply moving elements between threads and warps. Now that inferring the encoding is guaranteed to produce the given hint encoding if it is valid, we can check this with the existing verification code.
neildhar
added a commit
that referenced
this pull request
Apr 14, 2026
Reland of #9905. allowReorder reshapes still have a restriction that they cannot imply moving elements between threads and warps. Now that inferring the encoding is guaranteed to produce the given hint encoding if it is valid, we can check this with the existing verification code.
plognjen
pushed a commit
to plognjen/triton
that referenced
this pull request
Apr 14, 2026
allowReorder reshapes still have a restriction that they cannot imply moving elements between threads and warps. Now that inferring the encoding is guaranteed to produce the given hint encoding if it is valid, we can check this with the existing verification code.
plognjen
pushed a commit
to plognjen/triton
that referenced
this pull request
Apr 14, 2026
…d Revert "Verify allowReorder reshapes (triton-lang#9905)" (triton-lang#9983)
neildhar
added a commit
that referenced
this pull request
Apr 14, 2026
Reland of #9905. allowReorder reshapes still have a restriction that they cannot imply moving elements between threads and warps. Now that inferring the encoding is guaranteed to produce the given hint encoding if it is valid, we can check this with the existing verification code.
neildhar
added a commit
that referenced
this pull request
Apr 15, 2026
Reland of #9905. allowReorder reshapes still have a restriction that they cannot imply moving elements between threads and warps. Now that inferring the encoding is guaranteed to produce the given hint encoding if it is valid, we can check this with the existing verification code.
neildhar
added a commit
that referenced
this pull request
Apr 15, 2026
Reland of #9905. allowReorder reshapes still have a restriction that they cannot imply moving elements between threads and warps. Now that inferring the encoding is guaranteed to produce the given hint encoding if it is valid, we can check this with the existing verification code.
raymondtay
pushed a commit
to raymondtay/triton
that referenced
this pull request
Apr 18, 2026
Reland of triton-lang#9905. allowReorder reshapes still have a restriction that they cannot imply moving elements between threads and warps. Now that inferring the encoding is guaranteed to produce the given hint encoding if it is valid, we can check this with the existing verification code.
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
3 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.
allowReorder reshapes still have a restriction that they cannot imply
moving elements between threads and warps. Now that inferring the
encoding is guaranteed to produce the given hint encoding if it is
valid, we can check this with the existing verification code.