Skip to content

Add intel+cuda toolchain#1976

Merged
boegel merged 10 commits intoeasybuilders:developfrom
akesandgren:add-intel+cuda-toolchain
Nov 10, 2016
Merged

Add intel+cuda toolchain#1976
boegel merged 10 commits intoeasybuilders:developfrom
akesandgren:add-intel+cuda-toolchain

Conversation

@akesandgren
Copy link
Copy Markdown
Contributor

This is the framework part of a new intel+cuda toolchain.

The intention is that it should work the same way the gcc+cuda toolchain works.

@boegel boegel added this to the v3.0 milestone Nov 3, 2016
Comment thread easybuild/toolchains/intelc.py Outdated
"""Compiler toolchain with Intel compilers (icc/ifort), Intel MPI,
Intel Math Kernel Library (MKL), Intel FFTW wrappers and CUDA"""

NAME = 'intelc'
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@akesandgren hmm, won't this raise eyebrows w.r.t. naming? would intelcuda be better?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, i though of that too, but the other cuda enabled toolchains are also c, not cuda.

But, i'll leave it up to you as for the actual naming here...

comp_versions = {ec['name']: self.det_full_version(ec)}
if ec['name'] == 'ifort':
# 'icc' key should be provided since it's the only one used in the template
comp_versions.update({'icc': self.det_full_version(ec)})
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@akesandgren there's a lot of copy-pasting going on here, not a big fan of that

Also, I'd like to see this handled through a separate PR, preferably combined with #1753 which we should push through as well.
There's still an open question holding back that PR, but I feel that shouldn't be held back much longer...

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, i was a bit lazy writing that the first time around. Easy coding makes for fewer bugs :-)

Not quite sure what #1753 is trying to do though.

I can break this part out and make the rest of this a dependency on it if you really want that.

@akesandgren
Copy link
Copy Markdown
Contributor Author

Waiting for PR #1982 after which this one will be changed to depend on that instead.

'Clang,GCC': ('Clang-GCC', '%(Clang)s-%(GCC)s'),
'CUDA,GCC': ('GCC-CUDA', '%(GCC)s-%(CUDA)s'),
'CUDA,icc,ifort': ('intel-CUDA', '%(icc)s-%(CUDA)s'),
'CUDA,intel': ('intel-CUDA', '%(intel)s-%(CUDA)s'),
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@akesandgren is this last entry also required? I would expect that only the CUDA,icc,ifort entry is required for the iccifortcuda toolchain?

You are not combining intel with CUDA anywhere, only icc+ifort with CUDA?

fix broken test due to adding more test easyconfigs
@boegel
Copy link
Copy Markdown
Member

boegel commented Nov 10, 2016

Tested using easybuilders/easybuild-easyconfigs#3750, all good to go, thanks @akesandgren!

@boegel boegel merged commit e578f3b into easybuilders:develop Nov 10, 2016
@akesandgren akesandgren deleted the add-intel+cuda-toolchain branch November 10, 2016 21:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants