-
Notifications
You must be signed in to change notification settings - Fork 704
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
{lib}[gcccuda/2020b] NCCL v2.8.4-1 #12183
{lib}[gcccuda/2020b] NCCL v2.8.4-1 #12183
Conversation
Should we limit it to the cuda compute capabilities that we have?
|
Test report by @Flamefire |
Test report by @Flamefire |
Yes, but ideally that's done in a custom easyblock, may be difficult to do it cleanly in an easyconfig (i.e. handle the case when |
I think we can just fallback to passing nothing to the NCCL build and let NCCL build the fat binary. |
Test report by @verdurin |
Test report by @branfosj |
Test report by @branfosj |
Test report by @branfosj |
description = """The NVIDIA Collective Communications Library (NCCL) implements multi-GPU and multi-node collective | ||
communication primitives that are performance optimized for NVIDIA GPUs.""" | ||
|
||
toolchain = {'name': 'gcccuda', 'version': '2020b'} |
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'm thinking about the toolchain for this. Prior we had SYSTEM-CUDA, now (full)gcccuda, which means that it can't be used with Intel toolchains, can it?
So maybe GCCcore with CUDA dep and suffix?
Closing this. Using #13071 instead. |
(created using
eb --new-pr
)easyblock in
easybuilders/easybuild-easyblocks#2337and minor fix in easybuilders/easybuild-easyblocks#2460Fixes #12180