-
Notifications
You must be signed in to change notification settings - Fork 24.9k
Moved Autograd Fallback Interface to Header for Use by Out-of-tree Backends #159639
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
base: gh/fffrog/129/base
Are you sure you want to change the base?
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/159639
Note: Links to docs will display an error until the docs builds have been completed. ✅ You can merge normally! (1 Unrelated Failure)As of commit 799dc98 with merge base 8ab5868 ( UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
@pytorchbot label "topic: not user facing" |
@pytorchbot label "topic: not user facing" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will let @soulitzer review this one
Thank you. |
So sorry to you @soulitzer, could you help to take a look at this? |
Stack from ghstack (oldest at bottom):
As the title stated.
The new backend located in out-of-tree need to add custom operators as well,
so alse need to implemet autograd fallback.