-
Notifications
You must be signed in to change notification settings - Fork 741
Respect selective build for dtype_specialized_elementwise_fn_impl in elementwise_util #11975
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
|
Stack from ghstack (oldest at bottom): |
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/11975
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit e7fce3d with merge base 3d437c3 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This PR needs a
|
|
@swolchok has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
[ghstack-poisoned]
|
@swolchok has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
…elementwise_util (pytorch#11975) This fancy fast path I added didn't respect selective build. Now it should.
| CTYPE_OUT, | ||
| support_noncontiguous_tensors>(compute_fun, ctx, out, inputs...); | ||
| return; | ||
| if constexpr (should_include_kernel_dtype(op_name, compute_type)) { |
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.
I think I got this wrong in #11975 -- the compute_dtype is the one type that is NOT related to selective build.
I think I got this wrong in pytorch#11975 -- the compute_dtype is the one type that is NOT related to selective build.
This fancy fast path I added didn't respect selective build. Now it should.