Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29280 Discussions

Same code, different results from debug and release versions

Jon_D
New Contributor II
574 Views
I am converting a CVF project to IVF. The underlying source code is exactly the same. CVF Debug, CVF Release and IVF Debug give identical results. IVF Release gives slightly different results but enough to cause larger differences over many iterations. Then, in the IVF Release version I set Fortran > Run-time > Check Array and String Bounds to Yes and I get the same results as the other three versions (i.e. CVF debug, CVF release and IVF debug). As an alternative, I keep this setting as No but print out one of the variables that is suspect to cause the different results and I again get the same results as the other three. What is the reason for this? Is there a remedy?

Thanks for any help in advance,
Jon
0 Kudos
2 Replies
Steven_L_Intel1
Employee
574 Views
I'd guess a coding error that causes uninitialized or wrong data to be accessed. First thing to do is turn on Generate Interface Blocks and Check Routine Interfaces under Diagnostics if not already on. If it is on and you get no errors, then I'd try using the Static Verifier feature as described in the documentation.
0 Kudos
Jon_D
New Contributor II
574 Views
Thanks Steve,

Here is what I got from Static Verifier:

Performing static verification... ifort /Qdiag-enable:sv3 /nologo /Qdiag-enable:sv-include
... (list of .obj files)
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. ifort: error #10014: problem during multi-file optimization compilation (code 3)

Well, I guess it time to contact Premier Support.

Jon
0 Kudos
Reply