-
Notifications
You must be signed in to change notification settings - Fork 24.9k
[inductor] fix the unligned variable ranges issue in fuse node #138568
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/138568
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 54dcda8 with merge base f4ee5a2 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
aa53650
to
e4c22de
Compare
The new UT would fail for another fma VecN issue. Land after the fix: #138655. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CI failures. Can you also add a summary on the root cause of the issues and how you address it in the PR description?
e4c22de
to
c59e50c
Compare
Thanks! The failed UT triggers an issue about fma VectorizedN, which depends on the fix of #138655. The PR descriptions are updated. |
a446180
to
2a764fa
Compare
2a764fa
to
25ddbf3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
UT failures seem related?
25ddbf3
to
05cb2a7
Compare
05cb2a7
to
54dcda8
Compare
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
…ch#138568) Fixes pytorch#138550. ### Description In the fusion of two nodes, one node with less variables (`node_to_recomp`) would make its variable ranges aligned with the other node (`ref_node`). In detail, `node_to_recomp` would change its variable ranges to the original ranges of `ref_node`. However, if both of the nodes have changed its ranges, i.e., the simplified variable ranges are different from its original ones, the issue comes up. ### Solution For the case where the `ref_node` also changes its variable ranges, we recompute the size and body for it, to ensure the nodes are simplified to the same size. Pull Request resolved: pytorch#138568 Approved by: https://github.com/jgong5, https://github.com/leslie-fang-intel, https://github.com/jansel
Fixes #138550.
Description
In the fusion of two nodes, one node with less variables (
node_to_recomp
) would make its variable ranges aligned with the other node (ref_node
). In detail,node_to_recomp
would change its variable ranges to the original ranges ofref_node
. However, if both of the nodes have changed its ranges, i.e., the simplified variable ranges are different from its original ones, the issue comes up.Solution
For the case where the
ref_node
also changes its variable ranges, we recompute the size and body for it, to ensure the nodes are simplified to the same size.cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @chauhang @aakhundov