Back out "Better Shape Function Registration" #3261
Conversation
This file contains 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
Summary: For some reason, there are prod jobs that try to run fbgemm cuda ops on CPU, and rely on the ability to do so. This doesnt really make sense but we'll have to revert the shape registration refactor for now to enable it. As long as this interaction exists, we wont be able to support torch.export and these prod jobs at the same time. Reviewed By: jiawenliu64 Differential Revision: D64702422
|
This pull request was exported from Phabricator. Differential Revision: D64702422 |
✅ Deploy Preview for pytorch-fbgemm-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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.
Summary: For some reason, there are prod jobs that try to run fbgemm cuda ops on CPU, and rely on the ability to do so. This doesnt really make sense but we'll have to revert the shape registration refactor for now to enable it. As long as this interaction exists, we wont be able to support torch.export and these prod jobs at the same time.
Reviewed By: jiawenliu64
Differential Revision: D64702422