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

xilib: error #10014: problem during multi-file optimization compilation (code 3)

John6
Beginner
‎10-27-2009 10:22 AM
1,238 Views
Can anyone tell me why the attached simple FORTRAN(static lib) projectcannot seem to optimize (IVF 11.1.046)?
I turned on the "source code analysis" and I get the following:
------ Build started: Project: Test, Configuration: Debug Win32 ------
Performing source code analysis...
backend signals
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.
xilib: error #10014: problem during multi-file optimization compilation (code 3)
xilib: error #10014: problem during multi-file optimization compilation (code 3)
0 Kudos

Link Copied

6 Replies
Steven_L_Intel1
Employee
‎10-27-2009 10:52 AM
1,238 Views
You've found a bug in the source code analysis feature. It doesn't seem to like the ENTRY. I'll report it to the developrs.
0 Kudos
Copy link
Steven_L_Intel1
Employee
‎10-27-2009 01:03 PM
1,238 Views
You can turn off /check:bounds for this configuration and avoid the error. That's ok because you get no executable code anyway.
0 Kudos
Copy link
John6
Beginner
‎10-27-2009 01:05 PM
1,238 Views
You've found a bug in the source code analysis feature. It doesn't seem to like the ENTRY. I'll report it to the developrs.

Thanks. I have dealt with legacy code using (multiple) entries for years. I have noticed that IVF can bring Visual Studio down from time to time when debug stepping into FORTRAN entries (including v11.1.046). I was hoping that the source code analysis feature would point to areas where the code could be improved, and thus avoid the"Send Microsoft a Message" VStudio crashes.
0 Kudos
Copy link
Steven_L_Intel1
Employee
‎10-27-2009 01:16 PM
1,238 Views

I doubt there is much correlation with the sort of thing the source checker can find and what might trigger a VS crash. If you can provide us a test case that provokes a VS crash, please do so.

The issue ID for the compiler error is DPD200141271.
0 Kudos
Copy link
John6
Beginner
‎10-27-2009 01:57 PM
1,238 Views

I doubt there is much correlation with the sort of thing the source checker can find and what might trigger a VS crash. If you can provide us a test case that provokes a VS crash, please do so.

The issue ID for the compiler error is DPD200141271.
Yes, true. But I believe the problem is possibly concerningthe entriesor deferred-shape arrays. I did turn the array bounds checking off, and it did solve that problem, but the same sort of thing happens with another file, which I have greatly simplified down and attached (see Test2.zip). Again, the common element seems to be entries, possibly deferred-shape arrays, or possibly the Character*(*) declaration. And problemswith entrieshave caused megrief in the past, as I stated. The next time I have a VStudio crash, I'll investigate a little further and try to whittle it down a bit.
0 Kudos
Copy link
Steven_L_Intel1
Employee
‎04-30-2010 12:33 PM
1,238 Views
The xilib error will be fixed in the next major release. I can't access the zip you uploaded in the last reply.
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.