-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Virtual cuda #29782
Virtual cuda #29782
Conversation
The still rather big but slightly smaller single CUDA providing version of nvhpc. Co-authored-by: Wileam Y. Phan <wphan@vols.utk.edu>
Giant package that provides multiple versions of CUDA. Co-authored-by: Wileam Y. Phan <wphan@vols.utk.edu>
Rename cuda to cuda-toolkit and make it provide cuda. Co-authored-by: Wileam Y. Phan <wphan@vols.utk.edu>
Co-authored-by: Wileam Y. Phan <wphan@vols.utk.edu>
f132e9d
to
dcc2be7
Compare
@spackbot run pipeline |
I've started that pipeline for you! |
…, matched by libraries instead
I am drafting a long comment to this PR. Stay tuned. |
Maybe it's better to have the discussion in #19365, since this is "just" one way to close it (and nobody is subscribed here). |
Adding the new Regarding |
Below message was seen when I tried to execute following command: --snippet--
Command executed: Please guide me how to resolve above issue. |
@vkallesh Sorry for the late response, but would you mind creating a separate issue for this? You can pick "Build error" for the issue type, and the affected package is |
With this PR there are 3 packages providing CUDA:
cuda-toolkit
,nvhpc
andnvhpc-slim
.cuda-toolkit
: originally thecuda
packages, and it just "forwards" cudaversions
nvhpc
: provides multiplecuda
's as a version list, corresponding tothose from
cuda-toolkit
based on matching version.{json,txt}nvhpc-slim
: same asnvhpc
, except it only provides a single "latest"cuda
to reduce bandwidth & storage, and makes it easier to work withcompat bounds like
cuda@11.2:
This PR basically combines #29550 and #29155 (but provide cuda unconditionally) and #29742 and fixes #19365 for the most part.
As an example:
To me concretization makes sense for
cuda-toolkit
andnvhpc-slim
. For nvhpc, I'm not entirely convinced this behavior is great, it picks up the newest nvhpc because it happens to provide an old 10.x cuda toolkit. But the build system likely doesn't know how to pick it up, so maybe some work has to be done to get the correctnvcc
in the PATH (see e.g. https://cmake.org/cmake/help/latest/module/FindCUDAToolkit.html#search-behavior).