#2021: compiling Carpet fails with intel 17 and optimisation -----------------------------------------+---------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: new Priority: unset | Milestone: Component: Carpet | Version: Keywords: | -----------------------------------------+---------------------------------- Compiling carpet with intel 17.0.1 and -O2 or -O3 triggers an internal compiler error ("internal error: 0_76"). It only affects the file bbox.cc. Happened on two different clusters. ET version is Payne.
#2021: compiling Carpet fails with intel 17 and optimisation ------------------------------------------+--------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: new Priority: unset | Milestone: Component: Carpet | Version: Resolution: | Keywords: ------------------------------------------+---------------------------------
Comment (by rhaas):
Fixed in https://bitbucket.org/eschnett/carpet/pull-requests/16 in master.
#2021: compiling Carpet fails with intel 17 and optimisation ------------------------------------------+--------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: review Priority: unset | Milestone: Component: Carpet | Version: Resolution: | Keywords: backport ------------------------------------------+--------------------------------- Changes (by rhaas):
* keywords: => backport * status: new => review
Comment:
Does anyone object to backporting this commit to the release.
#2021: compiling Carpet fails with intel 17 and optimisation ------------------------------------------+--------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: review Priority: unset | Milestone: Component: Carpet | Version: Resolution: | Keywords: backport ------------------------------------------+---------------------------------
Comment (by eschnett):
Please backport.
#2021: compiling Carpet fails with intel 17 and optimisation ------------------------------------------+--------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: reviewed_ok Priority: unset | Milestone: Component: Carpet | Version: Resolution: | Keywords: backport ------------------------------------------+--------------------------------- Changes (by eschnett):
* status: review => reviewed_ok
#2021: compiling Carpet fails with intel 17 and optimisation ------------------------------------------+--------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: closed Priority: unset | Milestone: Component: Carpet | Version: Resolution: fixed | Keywords: backport ------------------------------------------+--------------------------------- Changes (by rhaas):
* status: reviewed_ok => closed * resolution: => fixed
Comment:
Applied as git hash 7309680e of Carpet.
#2021: compiling Carpet fails with intel 17 and optimisation ------------------------------------------+--------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: closed Priority: unset | Milestone: Component: Carpet | Version: Resolution: fixed | Keywords: backport ------------------------------------------+---------------------------------
Comment (by wolfgang.kastaun@…):
Replying to [comment:1 rhaas]:
Fixed in https://bitbucket.org/eschnett/carpet/pull-requests/16 in
master.
The fix worked for me, too.
#2021: compiling Carpet fails with intel 17 and optimisation ------------------------------------------+--------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: closed Priority: unset | Milestone: Component: Carpet | Version: Resolution: fixed | Keywords: backport ------------------------------------------+---------------------------------
Comment (by knarf):
Did anyone submit a ticket to Intel?
#2021: compiling Carpet fails with intel 17 and optimisation ------------------------------------------+--------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: closed Priority: unset | Milestone: Component: Carpet | Version: Resolution: fixed | Keywords: backport ------------------------------------------+---------------------------------
Comment (by anonymous):
Replying to [comment:7 knarf]:
Did anyone submit a ticket to Intel?
One would need to reproduce the problem with a small code. Someone got the same internal error code and submitted this: https://software.intel.com/en-us/forums/intel-c-compiler/topic/704437
No idea if this is the same problem.
#2021: compiling Carpet fails with intel 17 and optimisation ------------------------------------------+--------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: closed Priority: unset | Milestone: Component: Carpet | Version: Resolution: fixed | Keywords: backport ------------------------------------------+---------------------------------
Comment (by zachetie@…):
I suggest re-opening this ticket, as it is more serious than previously thought: Intel compiler version 18.0.1 20171018 produces the same failure, and the fix only applies if Intel 17.0.0 is used. Should be an easy fix to include Intel 18 as well. I would be surprised if all Intel compilers from 17.0.0 through 18.0.1 are *not* affected by this.
#2021: compiling Carpet fails with intel 17 and optimisation ------------------------------------------+--------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: reopened Priority: unset | Milestone: Component: Carpet | Version: Resolution: | Keywords: backport ------------------------------------------+--------------------------------- Changes (by rhaas):
* status: closed => reopened * resolution: fixed =>
#2021: compiling Carpet fails with intel 17 and optimisation ------------------------------------------+--------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: reopened Priority: unset | Milestone: Component: Carpet | Version: Resolution: | Keywords: backport ------------------------------------------+---------------------------------
Comment (by hinder):
We never reported it to Intel, so we shouldn't be too surprised. "anonymous" above claimed that reporting the problem to Intel required us to reproduce the problem with a small code. Is this true? These days, that seems like an unrealistic requirement. It should be possible to just give clear simple instructions for how to reproduce the problem (e.g. run GetComponents with a minimal thornlist, and compile). Does anybody know how to report the bug to Intel? 60 seconds with Google didn't lead to a clear answer; it seems you might have to have a support contract and contact them through that. I don't know how to do that here, and it would be much easier to just submit a form on a website.
#2021: compiling Carpet fails with intel 17 and optimisation ------------------------------------------+--------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: reopened Priority: unset | Milestone: Component: Carpet | Version: Resolution: | Keywords: backport ------------------------------------------+---------------------------------
Comment (by rhaas):
Maybe anonymous was me. The AEI has a support contract with Intel :-P
NCSA likely has through Cray and I think that we have at least some vulnerable compiler versions on BW.
If it really is a compile time ICE then a "big" code should also be ok. Plus one can likely strip out everything but Carpet, make a tarball of the pre-configured source code and hand that one to Intel.
#2021: compiling Carpet fails with intel 17 and optimisation ------------------------------------------+--------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: reopened Priority: unset | Milestone: Component: Carpet | Version: Resolution: | Keywords: backport ------------------------------------------+---------------------------------
Comment (by rhaas):
Encountered by Chia Hui Lin http://lists.einsteintoolkit.org/pipermail/users/2017-November/005904.html on edison using simfactory.
#2021: compiling Carpet fails with intel 17 and optimisation ------------------------------------------+--------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: review Priority: unset | Milestone: Component: Carpet | Version: Resolution: | Keywords: backport ------------------------------------------+--------------------------------- Changes (by rhaas):
* status: reopened => review
Comment:
This also affects Intel 18. I suggest to for now test for all intel compilers >= 17.00 and add the upper bound once we find a compiler that works again. I would also backport this to the release branch.
Namely use: {{{ // intel-17.0.0 fails with internal error 0_76 if vectorization is not disabled #if __INTEL_COMPILER >= 1700 #pragma GCC optimization_level 1 #endif }}} and would like to apply this very soon as stampede2's intel 18 compiler requires this and the next round of xrac allocation will come online on Jan 1st 2018.
#2021: compiling Carpet fails with intel 17 and optimisation ------------------------------------------+--------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: review Priority: unset | Milestone: Component: Carpet | Version: Resolution: | Keywords: backport ------------------------------------------+---------------------------------
Comment (by rhaas):
Any objections to the proposed patch? If none are voiced I will push the change on or after Jan 19 2018.
#2021: compiling Carpet fails with intel 17 and optimisation ------------------------------------------+--------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: review Priority: unset | Milestone: Component: Carpet | Version: Resolution: | Keywords: backport ------------------------------------------+---------------------------------
Comment (by hinder):
The comment in master, and in the patch proposed in comment:14, state that //vectorisation// needs to be disabled, and then go on to reduce the //optimisation// level to 1. Is this just a typo, and it should be "optimisation" in each case?
#2021: compiling Carpet fails with intel 17 and optimisation ------------------------------------------+--------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: review Priority: unset | Milestone: Component: Carpet | Version: Resolution: | Keywords: backport ------------------------------------------+---------------------------------
Comment (by rhaas):
I unfortunately do not know exactly how vectorization affects bbox.cc, though it could: Integer operations vectorize, not just floating point operations. Low optimization levels will not auto-vectorize code, which is independent of Cactus'/Carpet's/Vectors' vectorization which uses the vector builtins. So my best guess is that "vectorization" here means the auto-vectorization that the compiler does on higher levels of optimization (the size of the ivects etc in a bbox are known at compile time so they seem like good candidates for vectorization).
The original patch and comment is David Radice's.
#2021: compiling Carpet fails with intel 17 and optimisation ------------------------------------------+--------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: review Priority: unset | Milestone: Component: Carpet | Version: Resolution: | Keywords: backport ------------------------------------------+---------------------------------
Comment (by dradice):
It was meant to be "optimization" not "vectorization". It might be that the issue is indeed related to vectorization at the end.... I don't know.
#2021: compiling Carpet fails with intel 17 and optimisation ------------------------------------------+--------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: review Priority: unset | Milestone: Component: Carpet | Version: Resolution: | Keywords: backport ------------------------------------------+---------------------------------
Comment (by rhaas):
Ok, I'll fix the comment and push the commit later than. Nothing voiced so far sounds like an "objection" to me.
#2021: compiling Carpet fails with intel 17 and optimisation ------------------------------------------+--------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: review Priority: unset | Milestone: ET_2018_02 Component: Carpet | Version: Resolution: | Keywords: backport ------------------------------------------+--------------------------------- Changes (by hinder):
* milestone: => ET_2018_02
#2021: compiling Carpet fails with intel 17 and optimisation ------------------------------------------+--------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: review Priority: unset | Milestone: ET_2018_02 Component: Carpet | Version: Resolution: | Keywords: backport ------------------------------------------+---------------------------------
Comment (by rhaas):
Will backport to current release. Not sure why I have not pushed this yet.
#2021: compiling Carpet fails with intel 17 and optimisation ------------------------------------------+--------------------------------- Reporter: wolfgang.kastaun@… | Owner: eschnett Type: defect | Status: closed Priority: unset | Milestone: ET_2018_02 Component: Carpet | Version: Resolution: fixed | Keywords: backport ------------------------------------------+--------------------------------- Changes (by rhaas):
* status: review => closed * resolution: => fixed
Comment:
Applied as git commit 1378c7df "CarpetLib: fix comment about optimization in bbox.cc" and " db84c98c - CarpetLib: use O1 in bbox.cc for all Intel
17.0 compilers" of Carpet for the master branch, applied as git commit
a15fa600 "CarpetLib: fix comment about optimization in bbox.cc" and 703ac0d3 "CarpetLib: use O1 in bbox.cc for all Intel >17.0 compilers" for the ET_2017_06 branch of carpet.
trac@lists.einsteintoolkit.org
-
Einstein Toolkit