-
Notifications
You must be signed in to change notification settings - Fork 25.7k
[inductor] Flip custom_op_default_layout_constraint #135239
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
By default, Inductor should respect the stride order of input Tensors to custom operators. Test Plan: - new tests [ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/135239
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit f6b3cbe with merge base b7eb725 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
By default, Inductor should respect the stride order of input Tensors to custom operators. Test Plan: - new tests cc voznesenskym penguinwu EikanWang jgong5 Guobing-Chen XiaobingSuper zhuhaozhe blzheng wenzhe-nrv jiayisunx ipiszy yf225 chenyang78 kadeng muchulee8 ColinPeppler amjames desertfire chauhang [ghstack-poisoned]
By default, Inductor should respect the stride order of input Tensors to custom operators. Test Plan: - new tests cc voznesenskym penguinwu EikanWang jgong5 Guobing-Chen XiaobingSuper zhuhaozhe blzheng wenzhe-nrv jiayisunx ipiszy yf225 chenyang78 kadeng muchulee8 ColinPeppler amjames desertfire chauhang [ghstack-poisoned]
By default, Inductor should respect the stride order of input Tensors to custom operators. Test Plan: - new tests cc voznesenskym penguinwu EikanWang jgong5 Guobing-Chen XiaobingSuper zhuhaozhe blzheng wenzhe-nrv jiayisunx ipiszy yf225 chenyang78 kadeng muchulee8 ColinPeppler amjames desertfire chauhang [ghstack-poisoned]
By default, Inductor should respect the stride order of input Tensors to custom operators. Test Plan: - new tests [ghstack-poisoned]
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.
SGTM if we can land it!
|
I'm planning on landing this after the branch cut because it is relatively risky |
|
This config will only affect custom ops written by users, right? it will not have performance or correctness influence on the benchmarks in our dashboard, right? |
I don't know if there are custom ops in our dashboard. If there are any then it may affect them. So we can also watch the dashboard after merging this. |
|
@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 |
By default, Inductor should respect the stride order of input Tensors to custom operators. Test Plan: - new tests Pull Request resolved: #135239 Approved by: https://github.com/albanD ghstack dependencies: #135391
By default, Inductor should respect the stride order of input Tensors to custom operators. Test Plan: - new tests Pull Request resolved: pytorch#135239 Approved by: https://github.com/albanD ghstack dependencies: pytorch#135391
By default, Inductor should respect the stride order of input Tensors to custom operators. Test Plan: - new tests Pull Request resolved: pytorch#135239 Approved by: https://github.com/albanD ghstack dependencies: pytorch#135391
Stack from ghstack (oldest at bottom):
By default, Inductor should respect the stride order of input Tensors to
custom operators.
Test Plan:
cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @chauhang