Debug with fpe:0 Will Not Ignore Underflow

[jackosullivan1]

Using IVF 10.0(026) compiling with /fpe:0, which is supposed to mean "Underflow gives 0.0; Abort on other IEEE exceptions", my debug runs continue to interrupt at every blankety-blank instance of underflow, and I cannot get on to the real business at hand. All optimizations Disabled (/Od).

Even if I designate Debug / Exceptions / Win32 Exceptions / c0000093 Floating-point underflow as "Continue", the debugger stops, except that it then does it so deep down the call stack that I have no idea even where in my code I caused the underflow. (It stops at the correct code place if I replace "Continue" with "Break into the Debugger". But I don't want it to do that, just to obey my initial command to turn underflows into zeros and get on with it.)

Any help would be GREATLY appreciated.

Thanks so much and God bless!

Jack O'Sullivan

Property Page descriptions (besides /fpe:0)for Fortran Floating Point are:

FP Consistenct: Default Consistency; Round FP Results: No; Flush Denormal Results to Zero: Yes (/Qftz); Extend Precision of SP Constants: No; Enable IEEE Minus Zero Support: No; Limit COMPLEX Range: No; Check FP Stack: No; FP Speculation: Strict (/Qfp_speculationstrict)

Command Line (cut apart for readability here):

/nologo /Zi /Od /include:"Debug/" /fpscomp:filesfromcmd /fpscomp:ioformat
/fpscomp:logicals /fpscomp:general /warn:errors /warn:unused /warn:interfaces
/align:rec4byte /align:commons /assume:dummy_aliases /fpe:0
/Qftz /Qfp_speculationstrict /iface:cvf /module:"Debug/" /object:"Debug/"
/traceback /check:bounds /check:format /libs:qwin /c

[Steven_L_Intel1]

Since I see /libs:qwin I assume that the main program is Fortran, yes? I don't have an answer for you based on the description and would ask that you submit an issue to Intel Premier Support and attach a ZIP of a complete example (small if possible) that shows the problem.