[Fix][dlight] add an explicit reduction loop check in Reduce #17711
+32
−1
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
… since this is assumed in later stages
Member
|
Thanks for the fix. Could you please add regression test for it? |
prim funcs without a reduction loop
Hzfengsy
approved these changes
Mar 9, 2025
Member
|
Thanks @PatrikPerssonInceptron !! |
ShiboXing
pushed a commit
to ShiboXing/tvm
that referenced
this pull request
Aug 10, 2025
…17711) * added an explicit check to verify that the block has a reduction loop since this is assumed in later stages * added unit test to verify that the Reduction schedule is not applied to prim funcs without a reduction loop
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.
Added an explicit check in DLight Reduction to verify that the block has a reduction loop since this is assumed in later stages.