Skip to content
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

[BUG] example 06_splitK_gemm should allow post-Volta GPUs #1775

Open
lucifer1004 opened this issue Sep 4, 2024 · 2 comments
Open

[BUG] example 06_splitK_gemm should allow post-Volta GPUs #1775

lucifer1004 opened this issue Sep 4, 2024 · 2 comments

Comments

@lucifer1004
Copy link
Contributor

Describe the bug
Only Volta GPUs are allowed to run the example.

if (props.major != 7) {
std::cerr << "Volta Tensor Ops must be run on a machine with compute capability of 70, 72, or 75."

Steps/Code to reproduce bug
Run the compiled program on a machine with compute capability >= 80.

Expected behavior
The program should work on Volta and later GPUs.

Additional context
I have locally tested that this could work on 89.

@lucifer1004 lucifer1004 added ? - Needs Triage bug Something isn't working labels Sep 4, 2024
@lucifer1004 lucifer1004 changed the title [BUG] example 06_splitK_gemm should allow [BUG] example 06_splitK_gemm should allow post-Volta GPUs Sep 4, 2024
Copy link

github-actions bot commented Oct 4, 2024

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

Copy link

github-actions bot commented Jan 2, 2025

This issue has been labeled inactive-90d due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant