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.

Sign up for GitHub

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

Jump to bottom

cutlass 3.0 #11

Closed
fecet opened this issue Jul 31, 2023 · 3 comments · Fixed by #9
Closed

cutlass 3.0 #11

fecet opened this issue Jul 31, 2023 · 3 comments · Fixed by #9
Labels
question Further information is requested

Comments

@fecet
Copy link

fecet commented Jul 31, 2023

Comment:

Cutlass 3.0(3.1) have been released, should we support that?
@fecet fecet added the question Further information is requested label Jul 31, 2023
@h-vetinari
Copy link
Member

Yeah we should, but it's been stuck, see #9 & #7. I tried a fix for #9, let's see how it goes. Otherwise you're welcome to raise a PR and debug things! :)

@h-vetinari h-vetinari mentioned this issue Jul 31, 2023
Merged
3 tasks
@fecet
Copy link
Author

fecet commented Jul 31, 2023

I'm willing to contribute if I can provide some help :) But I'm quite new to conda-forge (I just install from it), can/should we use cuda from nvidia's channel?

@h-vetinari
Copy link
Member

No, we cannot use Nvidia's channel here. But the good thing is that the relevant parts of that channel are now moving to conda-forge anyway. Also, we managed to solve the issues and compilation timeouts, please let us know if anything is off with cutlass 3.1 (though you need CUDA >=12 for our current builds)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

cutlass v3.1.0 regro-cf-autotick-bot/cutlass-feedstock
2 participants
@h-vetinari @fecet