-
Notifications
You must be signed in to change notification settings - Fork 175
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
error #188: enumerated type mixed with another type #76
Comments
Interesting. I guess icc doesn't like enum compositions -- I'll see what I can do after installing the compiler. |
In the event that you are not fabulously wealthy, the Intel Free Software Tools page may be useful, particularly the program for open source contributors. |
It seems that icc fails to compile |
I am running on a 64-bit Cray XC40 supercomputer with Intel Haswell processors (NERSC Cori). > uname -a
Linux cori12 3.0.101-0.46-default #1 SMP Wed Dec 17 11:04:10 UTC 2014 (8356111) x86_64 x86_64 x86_64 GNU/Linux |
I fixed all the errors that icc raised, but ultimately I'm still having compilation issues with dyncall, which weirdly does not seem to happen on your end. Does everything works for you now? I'm going to ask on the dyncall mailing lists if I can do something about the dyncall/icc issue. |
It is possible that I have a patched version of CMake for this machine that works around dynamic library issues and that this has the side-effect of fixing this issue for me. Can you isolate the dyncall issue, i.e. give me the naked build command so I can try to reproduce what you see? |
Here's a full log of what's happening: http://paste.awesom.eu/raw/TylG However, I had to patch (see attached file) dyncall's CMakeLists.txt because it wouldn't add If left unpatched, the resulting log is very similar to what happens, except it fails when producing libdyncall_s.a, since the linker would not be able to relocate the object files. |
The naked command that fails to compile |
Ok, I fixed the issue locally and sent a patch upstream to dyncall. Criterion now compiles normally with icc/icpc. |
I understand that Intel 16 is not listed as a supported compiler on http://criterion.readthedocs.org/en/latest/setup.html#installation, but from what I can find online, this appears to be a valid compiler error.
I observe this when the Intel compiler is operating in GCC 4.3.0 and GCC 5.1.0 compatibility modes.
Thanks.
The text was updated successfully, but these errors were encountered: