-
Notifications
You must be signed in to change notification settings - Fork 24.7k
setitem node shouldn't be deadcode eliminated #145714
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
setitem node shouldn't be deadcode eliminated #145714
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/145714
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 7d23599 with merge base c6ad083 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
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.
Shouldn't have been in the graph in the first place...
@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 |
**Summary** Fix issue pytorch#145697. The `operator.setitem` has been eliminated as dead code, causing a correctness issue. Mark it as impure in this PR to avoid this side effect. **TestPlan** ``` python -u -m pytest -s -v test/fx/test_dce_pass.py -k test_keep_setitem ``` Pull Request resolved: pytorch#145714 Approved by: https://github.com/ezyang
Stack from ghstack (oldest at bottom):
Summary
Fix issue #145697. The
operator.setitem
has been eliminated as dead code, causing a correctness issue. Mark it as impure in this PR to avoid this side effect.TestPlan
cc @ezyang @SherlockNoMad @EikanWang @jgong5 @wenzhe-nrv