Intel 2018 Version 18.0.0.128 Build 20170811 "internal error"

[kostrzewa]

I don't know if this is a known problem, but it seems that QPhiX cannot currently be compiled with the Intel 2018 compiler.

When I try to link tmLQCD against QPhiX, compilation of our interface fails with an obscure error:

14:45 hch028@jrl04: ~/build/jurecabooster/2018_01_26/tmLQCD.etmc $ icc -V
Intel(R) C Intel(R) 64 Compiler for applications running on Intel(R) 64, Version 18.0.0.128 Build 20170811
Copyright (C) 1985-2017 Intel Corporation.  All rights reserved.

14:45 hch028@jrl04: ~/build/jurecabooster/2018_01_26/tmLQCD.etmc $ make qphix_interface.o
mpiicpc -DHAVE_CONFIG_H -I/homea/hch02/hch028/build/jurecabooster/2018_01_26/DDalphaAMG/include/ -I/homea/hch02/hch028/include/ -I. -I/homea/hch02/hch028/build/jurecabooster/2018_01_26/tmLQCD.etmc/  -I/homea/hch02/hch028/code/tmLQCD.etmc/ -I/homea/hch02/hch028/local/jurecabooster/libs/lime/include/ -I/homea/hch02/hch028/local/jurecabooster/libs/lemon/include/ -I/homea/hch02/hch028/local/jurecabooster/libs/QPhiX/include/ -I/homea/hch02/hch028/local/jurecabooster/libs/qmp/include/ -o qphix_interface.o -O3 -std=c++11 -qopenmp -xMIC-AVX512 -qopenmp -L/homea/hch02/hch028/lib -L./lib -L/homea/hch02/hch028/local/jurecabooster/libs/lime/lib/ -L/homea/hch02/hch028/local/jurecabooster/libs/lemon/lib -L/homea/hch02/hch028/build/jurecabooster/2018_01_26/DDalphaAMG/lib  -L/homea/hch02/hch028/local/jurecabooster/libs/QPhiX/lib -lqphix_solver -lqphix_codegen -L/homea/hch02/hch028/local/jurecabooster/libs/qmp/lib -lqmp -c /homea/hch02/hch028/code/tmLQCD.etmc/qphix_interface.cpp
": internal error: 20000_6735

compilation aborted for /homea/hch02/hch028/code/tmLQCD.etmc/qphix_interface.cpp (code 4)
make: *** [qphix_interface.o] Error 4

[bjoo]

Hi Bartosz, Yes, I found this also. I am sorry, I should’ve noted it as an issue, thanks for raising that. Best, B

…

On Jan 26, 2018, at 8:46 AM, Bartosz Kostrzewa ***@***.***> wrote: I don't know if this is a known problem, but it seems that QPhiX cannot currently be compiled with the Intel 2018 compiler. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

-------------------------------------------------------------------------------------- Dr Balint Joo High Performance Computational Scientist Jefferson Lab 12000 Jefferson Ave, Suite 3, MS 12B2, Room F217, Newport News, VA 23606, USA Tel: +1-757-269-5339, Fax: +1-757-269-5427 email: [email protected] -------------------------------------------------------------------------------------

[kostrzewa]

No worries, I had seen this before earlier this year also and similarly didn't raise it here... my apologies as well.

[bjoo]

If memory serves, I may have reported this to Intel via NERSC. @azrael417 do you remember, did we do this? Best, B

…

On Jan 26, 2018, at 9:25 AM, Bartosz Kostrzewa ***@***.***> wrote: No worries, I had seen this before earlier this year also and similarly didn't raise it here... my apologies as well. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

-------------------------------------------------------------------------------------- Dr Balint Joo High Performance Computational Scientist Jefferson Lab 12000 Jefferson Ave, Suite 3, MS 12B2, Room F217, Newport News, VA 23606, USA Tel: +1-757-269-5339, Fax: +1-757-269-5427 email: [email protected] -------------------------------------------------------------------------------------

[martin-ueding]

On the JURECA Booster there is now ICC version 2018.2.199-GCC-5.5.0. I have just managed to compile Chroma-QPhiX-QDP++ with it. So perhaps Intel has fixed whatever this bug was.

[bjoo]

Excellent. I should see if I can give it a try somewhere. ⁣Dr Balint Joo, Scientific Computing Group, Jefferson Lab,  Tel: +1 757 269 5339 (Office) Sent from my mobile phone​

…

On May 15, 2018, 5:21 PM, at 5:21 PM, Martin Ueding ***@***.***> wrote: On the JURECA Booster there is now ICC version 2018.2.199-GCC-5.5.0. I have just managed to compile Chroma-QPhiX-QDP++ with it. So perhaps Intel has fixed whatever this bug was. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_JeffersonLab_qphix_issues_115-23issuecomment-2D389317414&d=DwICaQ&c=lz9TcOasaINaaC3U7FbMev2lsutwpI4--09aP8Lu18s&r=SC-qvz5njMoFH6cliT5XZQ&m=Fz77L2G8b3bIglbmak7JWeqodjcQOlTRwfB1XP79g5E&s=BE-PhVts69Mv1_Au2rKEcNtgyXeCTc1Omb-DvRzcZ94&e=

[kostrzewa]

I can confirm that this now works also when linking QPhiX with tmLQCD using the compiler version noted by Martin: 18.0.2.199 Build 20180210

[kostrzewa]

Let's wait for Balint's test. Who knows if we're not just lucky at JSC...