forums.silverfrost.com

mecej4 · Joined: 31 Oct 2006 Posts: 1899

FTN95 7.1 on Windows 8.1 X64 runs into an internal error related to an FPU underflow exception when run on the code below, if before running the compiler the environment variable SALFENVAR is set equal to MASK_UNDERFLOW. The code is a severely stripped down version of DanRRight's code in a recent thread http://forums.silverfrost.com/viewtopic.php?t=3012 . The stripped down code will probably look silly, but the compiler is very sensitive to small changes to the code. In fact, rearranging the source code to interchange the order of the subroutines in the file (such that the subroutine with the comment "UNDERFLOW" appears second) makes the internal error go away.

PaulLaidler · Posted: Sat Feb 21, 2015 8:21 am Post subject:

Thanks for this. I have logged it for investigation.

PaulLaidler · Posted: Mon Feb 23, 2015 8:47 am Post subject:

At first sight there are two subroutines here that call other undefined subroutines, no main program. Did you intend that we go back to Dan's code in order to demonstrate this failure?

mecej4 · Joined: 31 Oct 2006 Posts: 1899

Thanks for looking at this, Paul.

This test code exposes a compiler error. It is not intended to be run or do anything useful. I obtained it by trimming Dan's rather long and complex example, which also did not contain a main program.

Normally, one does not expect compilation to be affected by compiler-specific environment variables that are documented for their effects on a running program that was compiled earlier. Here, there is an easy work around, but it is still an error that the compiler gets affected in an unexpected and undocumented way by the user's having previously set an environment variable to control the running of a user program.

PaulLaidler · Posted: Mon Feb 23, 2015 2:16 pm Post subject:

Thank you for this. If anyone can provide a small working program that illustrates the issue then we can progress from there.

mecej4 · Joined: 31 Oct 2006 Posts: 1899

Perhaps I did not stress this point enough: this report is not about an error that is encountered when running a user program. The faulting program is the compiler itself -- FTN95.EXE plus, possibly, its support DLLs.

Other vendors, such as Intel, would call such an error an Internal Compiler Error (ICE). In the presence of such an error, the compiler crashes, the compilation fails, so producing a working user program is impossible.

PaulLaidler · Posted: Mon Feb 23, 2015 2:38 pm Post subject:

Thanks. There is no confusion. No doubt there is an error in the FTN95 compiler and/or in salflibs.dll. We need a working program in order to trace the fault. The direct way to work is to step through FTN95 or salflibc.dll as they compile or run the given program.

davidb · Joined: 17 Jul 2009 Posts: 560 Location: UK

I think Paul is wrong here.

Here is a working version of the program (slightly changed)

From the command prompt
set SALFENVAR=MASK_UNDERFLOW
FTN95 code.f90 /LGO

silverfrost · Posted: Mon Feb 23, 2015 7:02 pm Post subject:

So it does.

PaulLaidler · Posted: Mon Feb 23, 2015 9:29 pm Post subject:

Thank you for the modified code. Hopefully this will be sufficient.

PaulLaidler · Posted: Tue Feb 24, 2015 1:29 pm Post subject:

This bug has been fixed for the next release.
In the short term the environment variable SALFENVAR should not be used for mask_underflow. Instead call mask_underflow@ at the start of your program. This has the same effect at run time.

A word of explanation...

FTN95.exe was failing because of a FPE when calculating statistics (e.g. the time taken to compile a program). This occurred in a call to DCLOCK@ and also in the calculation that followed.

The fix in the compiler is to undo the effect of this environment variable setting and (in salflibc.dll) to modify DCLOCK@ so that it is more robust.

mecej4 · Joined: 31 Oct 2006 Posts: 1899

Thanks for the quick response, and I appreciate being given the explanation.