Support exp op in XNNPACK backend #11803
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
leafs1
requested review from
digantdesai,
jackzhxng,
larryliu0820,
manuelcandales,
mcr229,
mergennachin and
swolchok
as code owners
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/11803
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 080c3df with merge base 124758e ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
facebook-github-bot
added
the
CLA Signed
leafs1
force-pushed
the
milestone3.2
branch
4 times, most recently
from
9a33a39 to
5e418e0
Compare
|
@pytorchbot label "release notes: none" |
pytorch-bot
bot
added
the
release notes: none
leafs1
force-pushed
the
milestone3.2
branch
5 times, most recently
from
108eaa5 to
27dce32
Compare
|
@leafs1 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
GregoryComer
approved these changes
Jun 23, 2025
GregoryComer
approved these changes
Jun 23, 2025
mcr229
approved these changes
Jun 24, 2025
|
@leafs1 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
|
@leafs1 has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
hinriksnaer
pushed a commit
to hinriksnaer/executorch
that referenced
this pull request
Jun 26, 2025
### Summary This PR adds support for the exp operator in ExecuTorch via XNNPACK, enabling optimized execution of torch.exp on the XNNPACK backend. The implementation includes updates to operator configuration, serialization, and runtime handling. The exp operator is now properly registered in the XNNPACK partition config and mapped to XNNPACK's xnn_create_exp_operator API in the compiler. ### Test plan I added a new test class TestExp that is a simple torch model with an exp op. It then asserts that the XNNPACK delegate was called while executing the exp op instead of the torch default exp op.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds support for the exp operator in ExecuTorch via XNNPACK, enabling optimized execution of torch.exp on the XNNPACK backend. The implementation includes updates to operator configuration, serialization, and runtime handling. The exp operator is now properly registered in the XNNPACK partition config and mapped to XNNPACK's xnn_create_exp_operator API in the compiler.
Test plan
I added a new test class TestExp that is a simple torch model with an exp op. It then asserts that the XNNPACK delegate was called while executing the exp op instead of the torch default exp op.