-
Notifications
You must be signed in to change notification settings - Fork 509
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
NOCOMMIT: PoC: vectorize just expm1 #9586
base: gh/swolchok/396/head
Are you sure you want to change the base?
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/9586
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 New Failures, 1 Cancelled JobAs of commit 6c7c0e6 with merge base 644b7dd ( NEW FAILURES - The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the `unary_ufunc_*` ops. ghstack-source-id: 94797d60df66089ebda3321a525d8a707be830f2 ghstack-comment-id: 2751961712 Pull Request resolved: #9586
Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the `unary_ufunc_*` ops. ghstack-source-id: 94797d60df66089ebda3321a525d8a707be830f2 ghstack-comment-id: 2751961712 Pull Request resolved: #9586
Here is how we can vectorize expm1 given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all the `unary_ufunc_*` ops. ghstack-source-id: e65c2b075587f716b8a746616d3335bab69a261d ghstack-comment-id: 2751961712 Pull Request resolved: #9586
I ran into an issue reordering diffs in a direct stack (the one currently ending in pytorch/executorch#9586) where GitHub's API complained `There are no new commits between base branch 'gh/swolchok/395/head' and head branch 'gh/swolchok/383/head'`. This seems to have fixed it for me.
I ran into an issue reordering diffs in a direct stack (the one currently ending in pytorch/executorch#9586) where GitHub's API complained `There are no new commits between base branch 'gh/swolchok/395/head' and head branch 'gh/swolchok/383/head'`. This seems to have fixed it for me.
I ran into an issue reordering diffs in a direct stack (the one currently ending in pytorch/executorch#9586) where GitHub's API complained `There are no new commits between base branch 'gh/swolchok/395/head' and head branch 'gh/swolchok/383/head'`. This seems to have fixed it for me.
#include <executorch/runtime/kernel/kernel_includes.h> | ||
#include <cmath> | ||
|
||
namespace torch { | ||
namespace executor { | ||
namespace native { | ||
|
||
// REVIEW: I'm not entirely sure what the best way to implement this |
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.
either the original vectorization PR or a preliminary PR will address this
Here is how we can vectorize
expm1
given the prior PRs in this stack. It is NOCOMMIT because we actually should implement vectorization for all theunary_ufunc_*
ops.