-
Notifications
You must be signed in to change notification settings - Fork 25.7k
use explicitly non-returning GPU atomics #60607
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
💊 CI failures summary and remediationsAs of commit de042d3 (more details on the Dr. CI page and at hud.pytorch.org/pr/60607):
🕵️ 3 new failures recognized by patternsThe following CI failures do not appear to be due to upstream breakages:
|
|
@ngimel has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator. |
|
Importing to see how internal builds go. |
|
@ngimel has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator. |
Summary: Enables an important performance optimization for ROCm, in light of the discussion in pytorch#41028. CC jithunnair-amd sunway513 Pull Request resolved: pytorch#60607 Reviewed By: jbschlosser Differential Revision: D29409894 Pulled By: ngimel fbshipit-source-id: effca258a0f37eaefa35674a7fd19459ca7dc95b
Enables an important performance optimization for ROCm, in light of the discussion in #41028.
CC @jithunnair-amd @sunway513