Intel® C++ Compiler
Community support and assistance for creating C++ code that runs on platforms based on Intel® processors.
7956 Discussions

link issue with ipo and oneAPI compiler : internal error 010101_3096

FredG
Beginner
927 Views

Hello, 

 

While we had no problems with the 2018 and 2016 versions of the intel compilers when we compiled with IPO option, with oneApi 2021 an internal error occurs during the linking step. 

": internal error: 010101_3096

icpc: error #10014: problem during multi-file optimization compilation (code 4)

 

we tried to make the link with icc and xild, the same error occurs.

we use the following flags to compile : -ipo -fno-fat-lto-objects

Do you know this error and ideally a way to remedy it?

 

icc / icpc version 2021.4.0 20210910

 

Thanks, 

Fred.

 

 

 

 

 

0 Kudos
4 Replies
DitiD_Intel
Moderator
901 Views

Hi,

 

Thank you for posting in Intel Communities.

 

>> Do you know this error and ideally a way to remedy it?

 

We've tried compiling a sample code on our system and it is working fine with 2021.4.

 

Please refer to the screenshot attached below.

 

Please find the source code of our sample attached. Also, please find below the steps to compile the same.

 

 

icpc link.cpp -c -std=c++17 -ipo -fno-fat-lto-objects -o link.o
icpc link.o -o IntelBug

 

Also, can you please provide a sample reproducer (steps if any) or is your reproducer similar to that of ours?

 

Thanks and Regards,

Ditipriya.

 

 

0 Kudos
FredG
Beginner
886 Views

Hi, 

 

Thank you Ditipriya for your answer.

Unfortunately our code (c++11) is confidential and its volume is too large to share.

Do you have any information about the internal error code (010101_3096) that would allow us to isolate and understand the problem ?

 

I just tried with the latest version 2021.5.0 present in the 2022 toolkit, the same error came up.

 

Thanks, 

Fred.

0 Kudos
FredG
Beginner
845 Views

Hello, 

 
We have found a workaround to solve the problem and compile without error with IPO and oneApi solution, we replaced the compilation option "-march=core-avx2" by "-axCORE-AVX2".
 
Regards, 
Fred. 
0 Kudos
DitiD_Intel
Moderator
824 Views

Hi,


Glad to know that your issue is resolved. Thanks for sharing the solution with us. If you need any additional information, please post a new question as this thread will no longer be monitored by Intel.


Thanks and Regards,

Ditipriya.




0 Kudos
Reply