Quantcast
Channel: Intel® Software - Intel® Visual Fortran Compiler for Windows*
Viewing all articles
Browse latest Browse all 5691

Compiling option /od introduce results difference between the release mode and bebug mode

$
0
0

I am maintaining a big code. I cannot upload the case. I found that /od is the reason for the results difference between release mode and debug mode.

In release mode, the compiling option is

 /nologo /real_size:64 /module:"x64\Release\\" /object:"x64\Release\\" /libs:static /threads /c

In debug mode, the compiling option is

 /nologo /debug:full /Od /gen-interfaces /warn:interfaces /real_size:64 /Qsave /module:"x64\Debug\\" /object:"x64\Debug\\" /traceback /check:bounds /check:uninit /libs:static /threads /dbglibs /c

Our code passed successfully using both compiling options but get different results after many iterations.

When I add /od in release mode, I found that the two results become same.

Can anyone explain why this code optimization option /od introduce the difference?

As a result, I found that the running speed becomes slower. So what coding part I should pay attention or update to remove this difference also running faster.

Thanks!


Viewing all articles
Browse latest Browse all 5691

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>