Fix IR generation conflict in topi.nn.simplify by separating Tensor and PrimExpr handling #17978
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
Hzfengsy
approved these changes
Jun 2, 2025
ShiboXing
pushed a commit
to ShiboXing/tvm
that referenced
this pull request
Aug 10, 2025
…nd PrimExpr handling (apache#17978) Update utils.py
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.
Fix #17847.
As described in #17847, the current topi.nn.simplify function incorrectly reuses input buffer names when simplifying
te.Tensor, causing IR generation conflicts in storage_rewrite.This PR modifies simplify to explicitly handle
te.Tensorinputs by generating a new output tensor (avoiding buffer aliasing), while preserving the original behavior for PrimExpr and scalar inputs.cc @tqchen @Hzfengsy @vinx13