Support exp op in XNNPACK backend #11803
Open
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.