-
Notifications
You must be signed in to change notification settings - Fork 23.1k
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
attempted fix for nvrtc with lovelace #87611
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/87611
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 40f84e1: This comment was automatically generated by Dr. CI and updates every 15 minutes. |
@@ -893,6 +893,8 @@ void codegenOutputQuery( | |||
max_dev_version = CUDAVersion(7, 5); | |||
} else if (nvrtc_version == CUDAVersion(11, 0)) { // 11.0 supports 3-8.0 | |||
max_dev_version = CUDAVersion(8, 0); | |||
} else if (nvrtc_major == 11 && nvrtc_minor < 8) { |
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.
} else if (nvrtc_major == 11 && nvrtc_minor < 8) { | |
} else if (nvrtc_major == 11 && nvrtc_minor <= 8) { |
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.
BUt versions less than 11.8 support only up to sm_86, so it's like this on purpose, or is my reasoning wrong?
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.
I thought nvrtc from 11.8 does not support sm_89, as well, does it?
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.
I believe this should work, as I've tested a similar fix with an older CUDA version previously as well CC @ptrblck |
@pytorchbot merge -g |
Merge startedYour change will be merged once all checks on your PR pass since you used the green (-g) flag (ETA: 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
@pytorchbot merge -f "low risk change that's not tested in CI anyway" |
The merge job was canceled. If you believe this is a mistake,then you can re trigger it through pytorch-bot. |
@pytorchbot merge -f "low risk change that's not tested in CI anyway" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Fixes pytorch#87595 (maybe?) Pull Request resolved: pytorch#87611 Approved by: https://github.com/malfet, https://github.com/atalman
Hey @ngimel. |
Fixes #87595 (maybe?) Pull Request resolved: #87611 Approved by: https://github.com/malfet, https://github.com/atalman Co-authored-by: Natalia Gimelshein <ngimel@fb.com>
Will this be in torch 1.13? |
Fixes pytorch#87595 (maybe?) Pull Request resolved: pytorch#87611 Approved by: https://github.com/malfet, https://github.com/atalman
Fixes pytorch#87595 (maybe?) Pull Request resolved: pytorch#87611 Approved by: https://github.com/malfet, https://github.com/atalman
Fixes #87595 (maybe?)