Table 10 Values for the +FP option (continued)
Value Meaning
ITrap on
DEnable sudden underflow (flush to zero) of denormalized values on those
+[no]fp_exception +fp_exceptionis a compile time flag. It causes a descriptive message and a procedure traceback to be issued to standard error when the
For a description of these signals, see signal(2) and signal(5) in the
You can also use the ON statement to write your own trap procedures. For information about the syntax of the ON statement, see “Using the ON statement” (page 81).
The default,+nofp_exception , disables traceback information.
Table 11 Signals recognized by the +fp_exception option
Signal |
| Meaning |
SIGILL |
| Illegal instruction |
|
|
|
SIGFPE |
| |
|
|
|
SIGBUS |
| Bus error instruction |
|
|
|
SIGSEGV |
| Segmentation violation |
|
|
|
SIGSYS |
| Bad argument to system call |
|
|
|
| can be used to prepare code for debugging that has been compiled with optimization | |
| ||
+getarg0and +getarg1control the behavior of the getarg intrinsic subroutine. +getarg0 | ||
| requests the industry standard behavior for getarg, where an index value of zero causes the | |
| program name to be returned. HP’s FORTRAN 77 getarg intrinsic also implements this industry | |
| standard convention. +getarg1is used to request | |
| of one causes the program name to be returned (older releases of HP Fortran behaved in this | |
| manner). The default is +getarg0. | |
gformat77 | gformat77 requests the FORTRAN 77 style of formatting a value of zero with the G edit | |
| descriptor. Fortran 90 uses an F edit descriptor when the value being written is zero, while | |
| FORTRAN 77 uses an E edit descriptor. | |
+[no]gprof | +gprof prepares object code files for profiling with gprof. The default is +nogprof. gprofis | |
| provided as part of the | |
| ||
+hugecommon | +hugecommon instructs the compiler to place the specified COMMON block into a huge data | |
| segment. The format for this option is: +hugecommon=name | |
| where name is the name of a COMMON block. By default, only COMMON blocks larger than | |
| 2 gigabytes are placed into huge data segments. | |
| For example: |
28 Compiling and linking