-
Notifications
You must be signed in to change notification settings - Fork 25.6k
[CUDA][CUTLASS] CUTLASS 3.9 submodule upgrade #151253
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🧪 See artifacts and rendered test results at hud.pytorch.org/pr/151253
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 2656eb6 with merge base 982062d ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
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 was about to do this. <3
@eqy since CUTLASS isn't pinned yet, can we fix the curr_stride bugs upstream? Issue opened: NVIDIA/cutlass#2253 |
cc @henrylhtsang since you already have some internal patches |
Let's try to land it |
@pytorchmergebot merge |
This PR updates submodules third_party/cutlass If those updates are intentional, please add "submodule" keyword to PR title/description. |
@pytorchmergebot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Originally authored by Jack Kosaian, likely needs #ifdefs if we want to preserve compat with 3.8
cc @H-Huang @awgu @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @ptrblck @msaroufim @jerryzh168