Ship the merged CPU kernels as their own library - #21524
Open
shoumikhin wants to merge 61 commits into
Open
Conversation
Contributor
Author
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/21524
Note: Links to docs will display an error until the docs builds have been completed. This comment was automatically generated by Dr. CI and updates every 15 minutes. |
This was referenced Jul 31, 2026
This was referenced Jul 31, 2026
This was referenced Aug 4, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The CPU operator kernels are compiled into whichever component links
them. The Python extension therefore carries a full private copy, which makes it large, and a
C++ application cannot get the same operators without building them from source.
There is a correctness reason too, not just size. Operators register themselves into a table
when their library loads. Two copies in one process means two independent registrations of the
same operator set, and which one a model resolves to is then a matter of load order.
How you use it
The target name is the contract, not the file name. A model running the usual CPU operators
needs nothing else.
Tested
Built the wheel on Linux x86_64 and aarch64, installed it into a clean environment, and
confirmed by symbol inspection that exactly one shipped library registers the CPU operator set.
Linked a C++ application against the component, ran a model through it, and ran the existing
Python tests so current users are unaffected.