Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
180 Views

Errors migrating project from Intel C++ XE 2018 to Intel 19.1

A project that has been compiling OK with Intel C compilers sing 2013 and I am using very well with XE 2018 update 5 fails if I try with compiler 2019.1.

If using Multi-file optimization /Qipo:

1>
1>": : error : 010101_0
1>
1>xilink: : error #10014: problem during multi-file optimization compilation (code 4)
1>xilink: : error #10014: problem during multi-file optimization compilation (code 4)
1>Done building project "MNPS.vcxproj" -- FAILED.
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========

And:

Severity Code Description Project File Line Suppression State
Error (active) E1696 cannot open source file "dfp754.h" MNPS C:\Program Files (x86)\IntelSWTools\compilers_and_libraries_2020\windows\compiler\include\mathimf.h 260
Error (active) E0081 more than one storage class may not be specified MNPS C:\ALA64_10\sdlMNPS\DBS_E_Field.C 121
Error (active) E0081 more than one storage class may not be specified MNPS C:\ALA64_10\sdlMNPS\DBS_E_Field.C 1494
Error (active) E0411 a parameter is not allowed MNPS C:\ALA64_10\SDL\wat.h 230
Error (active) E0411 a parameter is not allowed MNPS C:\ALA64_10\SDL\wat.h 230
Error (active) E0411 a parameter is not allowed MNPS C:\ALA64_10\SDL\wat.h 230
Error (active) E0411 a parameter is not allowed MNPS C:\ALA64_10\SDL\wat.h 230
Error 010101_0 MNPS C:\ALA64_10\sdlMNPS\MNPS\MNPS\": 1
Error #10014 problem during multi-file optimization compilation (code 4) MNPS 1
Error #10014 problem during multi-file optimization compilation (code 4) MNPS 1

 

If changed to Single-file /Qip, it compiles but some floating-point parts produce bad results.

Changing the project to XE 2018 everything is perfect.

 

Any idea?

Thanks.

 

Labels (1)
0 Kudos
4 Replies
Highlighted
177 Views

In case the compilation log helps it is attached here.

0 Kudos
Highlighted
160 Views

Additional information. Compiling with Intel 19.1 in DEBUG mode everything works well.

The error/bug is associated with code optimization in Intel® C++ Compiler 19.1.

NOTE: My source is C99 ( /Qstd=c99 ) including careful use of VLA.

0 Kudos
Highlighted
Moderator
148 Views

Hi Armando,


This issue seems like a bug.

Hence we are forwarding this to the concerned internal team.


Regards

Prasanth


0 Kudos
Highlighted
145 Views

Hi Prasanth,

Thank you for your reply.

A new test compiling with 19.1 and optimization as /O1 produces good code and results.

I just downgrade to Intel C++ Compiler XE 18.0 until I receive news about the issue.  Fortunately, the integration of Intel (and Clang) with VisualStudio 2019 is very friendly turning easy the switch between compiler platforms.

 

 

 

0 Kudos