-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Tracking updates for CUDA 11.3 and 11.4 #58
Comments
I am working on this now! 💪 |
Ok, that's it for now, sans the migrator. We need to wait on The Windows part should be self-sufficient. |
We should get #48 done before starting the migrator. Now that we have big packages like pytorch which needs manual compilations, it's a waste of developer time to build them for 11.3 when only packages that depend on nvrtc need to be rebuilt. |
Fair enough! I'll comment on the issue then. |
Might as well make this a double-issue like #47 was: https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html |
I'll add the relevant metadata but we still need to decide whether we split or not (#48). |
NVIDIA Docker images were uploaded end of last week. Jaime updated the Docker PR to include 11.4. Those builds seem to work except for the fact that |
What's the status here not that conda-forge/nvcc-feedstock#71 has been merged? |
Oh this is done. We now use CUDA Enhanced Compatibility to build with 11.2 and then allow users to install any |
Would like to do an announcement/blogpost, but wanted to complete |
OK, so we don't need newer nvcc builds in conda-forge (I get that it's possible to build for 11.4 with 11.2)? If so, should this issue be closed? Would you be able to comment on the PTX-vs-ABI situation (and possibility to opt out of Enhanced Compatibility) in conda-forge/nvcc-feedstock#71? |
Yeah exactly. Sure :) That's already discussed earlier in that PR. Not sure what is meant by opt-out. Maybe a new issue would be better for discussing other things? |
CUDA 11.3 was released a while ago. Opening this issue to track roll-out, using the pattern from #47
11.3 / 11.4
Also ref to the docs for adding a new version.
CC @jaimergp
The text was updated successfully, but these errors were encountered: