Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29277 Discussions

Fatal error 'Performing static verification'

warwickb1
Beginner
596 Views

I have had a "severe" error and a request to provide a "Software Problem Report".

The message was:


1>Performing static verification...
1>101006_4001
1>Severe: **Internal compiler error: internal abort** Please report this error along with the circumstances in which it occurred in a Software Problem Report. Note: File and line given may not be explicit cause of this error.
1>ifort: error #10014: problem during multi-file optimization compilation (code 3)
1>
1>Build log written to "file://I:binGroundInGroundInDialogGroundRelateDebugBuildLog.htm"
1>GroundRelate-1-2-0 - 1 error(s), 1 warning(s)
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

According to the file "fsupport.txt" I am using Package ID: W_FC_P_10.0.025

I have reported this to Premium Support but they don't seem to be aware of any issue and want a 'reproducer'.

I am hoping you may know if I need an upgrade, or it this is new to you too?

I get around the issue by not using this verification option within MS Visual Studio.

0 Kudos
1 Solution
TimP
Honored Contributor III
596 Views
Yes, a current compiler would be useful, particularly if you like that option (which was renamed as /Qdiag-enable:sc). It still has a few bugs, which I have tripped over in my reports on this forum. If you find bugs, it is important to include a test case (the "circumstances") in your report.

View solution in original post

0 Kudos
1 Reply
TimP
Honored Contributor III
597 Views
Yes, a current compiler would be useful, particularly if you like that option (which was renamed as /Qdiag-enable:sc). It still has a few bugs, which I have tripped over in my reports on this forum. If you find bugs, it is important to include a test case (the "circumstances") in your report.
0 Kudos
Reply