Compilation options & crashes.

Intel® Fortran Compiler

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

Compilation options & crashes.

620 Views

I have an application that compiles & runs just fine as long as /dbglibs is specified at compile-time. It works fine with:

/dbglibs /debug:full /pdbfile

as well as with

/dbglibs /optimize:5

but if I try /nodbglibs with either of them, I get an access violation.

For the same program, if I specify /unroll:n where n>0, the program will crash unless /check:bounds is also called.

So are these interactions reasonable to those more learned? I've found workarounds, so its not a big deal; but is seems quite odd.

Matt.

Link Copied

0 Replies

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.