-
Notifications
You must be signed in to change notification settings - Fork 26.3k
[PyTorch] Only select root ops in codegen unboxing #74663
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
🔗 Helpful links
💊 CI failures summary and remediationsAs of commit 5585405 (more details on the Dr. CI page):
1 failure not recognized by patterns:
🚧 1 fixed upstream failure:These were probably caused by upstream breakages that were already fixed.
Please rebase on the
|
|
This pull request was exported from Phabricator. Differential Revision: D35104401 |
1 similar comment
|
This pull request was exported from Phabricator. Differential Revision: D35104401 |
a8043e1 to
e7c825d
Compare
…ch (pytorch#74664) Summary: This change adds the following logic: If lightweight dispatch is enabled, do not generate `TORCH_LIBARAY` API calls for operator schema and implementations, since these operators will be registered into JIT op registry. `skip_dispatcher_op_registration` is an existing argument to `gen.py`. With that set, `RegisterDispatchKey.cpp` will not generate `m.def` and `m.impl` for each native function. This logic will be removed once we find a better way to skip op registration into dispatcher. Pull Request resolved: pytorch#74664 Test Plan: Rely on unit tests for lightweight dispatch. Reviewed By: priyaramani Differential Revision: D34634300 Pulled By: larryliu0820 fbshipit-source-id: 2882b96b30c8e6edadb6efa065c6310747cc08dc
Summary: Pull Request resolved: pytorch#74663 In lightweight dispatch, we only need to register root ops. Unlike in the dispatcher world, the transitive closure of the operators doesn't need to go through dispatcher or op registry. Test Plan: Rely on unit tests Reviewed By: priyaramani Differential Revision: D35104401 fbshipit-source-id: c5e9d64b866d92135a11cad2f10adb63701edda7
|
This pull request was exported from Phabricator. Differential Revision: D35104401 |
e7c825d to
5585405
Compare
Summary: Pull Request resolved: #74663 In lightweight dispatch, we only need to register root ops. Unlike in the dispatcher world, the transitive closure of the operators doesn't need to go through dispatcher or op registry. Test Plan: Rely on unit tests Reviewed By: priyaramani Differential Revision: D35104401 fbshipit-source-id: 1a2df571880ac3c8625985c01bd89a2bb9566af9
|
Hey @larryliu0820. |
Summary: Pull Request resolved: #74663 In lightweight dispatch, we only need to register root ops. Unlike in the dispatcher world, the transitive closure of the operators doesn't need to go through dispatcher or op registry. Test Plan: Rely on unit tests Reviewed By: priyaramani Differential Revision: D35104401 fbshipit-source-id: 1a2df571880ac3c8625985c01bd89a2bb9566af9 (cherry picked from commit 16207fa)
Summary: In lightweight dispatch, we only need to register root ops. Unlike in the dispatcher world, the transitive closure of the operators doesn't need to go through dispatcher or op registry.
Test Plan: Rely on unit tests
Differential Revision: D35104401