{toolchain}[dummy] intel 2016.02-GCC-5.3 (REVIEW) #2523
Conversation
| toolchain = {'name': 'dummy', 'version': 'dummy'} | ||
|
|
||
| compver = '2016.2.181' | ||
| gccver = '4.9.3' |
|
missing icc/2016.2.181 et al? btw. whichever GCC you pick, let's please make sure that it can build at least essentials/classics, |
|
Easyconfigs unit test suite FAILed. See https://jenkins1.ugent.be/job/easybuild-easyconfigs-pr-builder/6318/console for more details. Please fix the reported issues by pushing additional commits to the branch corresponding with this pull request; contact @boegel if you're not sure what to do. |
|
@fgeorgatos: yeah, just getting started, I'd like to get some feedback on the GCC part in here first... |
boegel
changed the title
|
Easyconfigs unit test suite FAILed. See https://jenkins1.ugent.be/job/easybuild-easyconfigs-pr-builder/6631/console for more details. Please fix the reported issues by pushing additional commits to the branch corresponding with this pull request; contact @boegel if you're not sure what to do. |
|
Test report by @boegel |
|
building HPL on top of Are we good to go through with these latest Intel 2016 compilers on top of GCC v5.3.0? |
|
Is this intel update compatible with GCC 5? I can't find anything in the release notes. |
| ] | ||
|
|
||
| # full list of components can be obtained from pset/mediaconfig.xml in unpacked sources | ||
| # cfr. https://software.intel.com/en-us/articles/intel-composer-xe-2015-silent-installation-guide |
There was a problem hiding this comment.
maybe mention that this is a list of regex and not a regular list of components?
|
@ocaisa: cfr. #2100 (comment) |
|
Easyconfigs unit test suite FAILed. See https://jenkins1.ugent.be/job/easybuild-easyconfigs-pr-builder/6667/console for more details. Please fix the reported issues by pushing additional commits to the branch corresponding with this pull request; contact @boegel if you're not sure what to do. |
So GCC 5.1 seems to be officially supported now, but >5.1 not. |
|
@damianam: any chance that part of the page was last updated when GCC 5.1 and binutils 2.25 were latest and greatest? |
|
Yes, could be. The website says July 6 2015, 10 days before GCC 5.2 was released. But intel 2016 update 2 has been released just a few days ago I think, so it could very well be that the original post was made in July 6 for intel 2016, and kept the date later on for the update 1 and update 2. In any case it is unclear if the update 2 works with 5.3, but it is clear that it works with 5.1. Maybe taking a look at the list of changes 5.1->5.3 can help to figure out if it is truly compatible or not. My guess is that it will work, but if it doesn't we are on our own, without official support. |
| easyblock = "Toolchain" | ||
|
|
||
| name = 'intel' | ||
| version = '2016.02' |
There was a problem hiding this comment.
good and useful PR, nice to see it merged.
As said during meeting today: it would be good to have a -GCC-5.3.0 suffix, to make room for -GCC-4.9.3
There was a problem hiding this comment.
yeap, thanks for the GCC-4.x PR.
IMHO, binutils/2.26 would likely be preferable by EB community,
in the name of supporting more architectures;
this might, just might, make it less of an issue the 5.1 vs 5.3 debate... (fingers crossed)
boegel
changed the title
|
Easyconfigs unit test suite FAILed. See https://jenkins1.ugent.be/job/easybuild-easyconfigs-pr-builder/6742/console for more details. Please fix the reported issues by pushing additional commits to the branch corresponding with this pull request; contact @boegel if you're not sure what to do. |
|
visual review OK, btw |
|
Easyconfigs unit test suite FAILed. See https://jenkins1.ugent.be/job/easybuild-easyconfigs-pr-builder/7119/console for more details. Please fix the reported issues by pushing additional commits to the branch corresponding with this pull request; contact @boegel if you're not sure what to do. |
|
Easyconfigs unit test suite FAILed. See https://jenkins1.ugent.be/job/easybuild-easyconfigs-pr-builder/7124/console for more details. Please fix the reported issues by pushing additional commits to the branch corresponding with this pull request; contact @boegel if you're not sure what to do. |
|
Test report by @boegel |
|
Test report by @boegel |
|
Easyconfigs unit test suite PASSed (see https://jenkins1.ugent.be/job/easybuild-easyconfigs-pr-builder/7920/console for more details). This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
|
I've opened a support ticket with Intel to ask for an official statement w.r.t. compatibility of Intel 2016 update 2/3 with GCC 5.3 and 6.1. However, I don't expect any surprises here; if they claim to be compatible with GCC 5.1, they should also be compatible with 5.3 (which is basically a bugfix-only release of GCC 5.1); if anything, compatibility should be better. So, I propose we go ahead with this (and #3009) and merge this in. |
|
I got official word from Intel support that Intel compilers version 2016 update 3 is compatible with GCC 5.3 (for future reference: issue ID 6000160708). I didn't ask for compatibility of version 2016 update 2 with GCC 5.3, but since https://software.intel.com/en-us/articles/intel-c-compiler-160-for-linux-release-notes-for-intel-parallel-studio-xe-2016 mentions compatibility with GCC 5.1, and the fact that GCC 5.3 is bugfix release over GCC 5.1, I think it's safe to assume that this combo should also be fine. So, this is good to go imho. Thanks a lot for the feedback @fgeorgatos, @ocaisa, @damianam and @wpoely86! |
depends on
#2524