HP Fortran Programmer Guide HP-UX 11i v1, HP-UX 11i v2, and HP-UX 11i v3 (B3908-90032,December 2012)

For a description of these signals, see signal(2)and signal(5)in the HP-UX Reference. For
information about floating-point exceptions and error handling, see the HP-UX Floating-Point
Guide.
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” on page 127.
The default,+nofp_exception , disables traceback information.
Table 11 Signals recognized by the +fp_exception option
MeaningSignal
Illegal instructionSIGILL
Floating-point exceptionSIGFPE
Bus error instructionSIGBUS
Segmentation violationSIGSEGV
Bad argument to system callSIGSYS
-gcauses the compiler to generate information for use by the HP WDB debugger. The -goption
can be used to prepare code for debugging that has been compiled with optimization
options-O,-O1/+O1, , but not O3/+O3or higher.
-g
+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
-G
program name to be returned. HP’s FORTRAN 77 getarg intrinsic also implements this industry
standard convention. +getarg1is used to request non-standard behavior, where an index value
of one causes the program name to be returned (older releases of HP Fortran behaved in this
manner). The default is +getarg0.
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.
gformat77
+gprof prepares object code files for profiling with gprof. The default is +nogprof. gprofis
provided as part of the “HP-UX General Programming Tools” product; see gprof(1). The
-Goption can be used to perform the same function as +gprof.
+[no]gprof
+hugecommon instructs the compiler to place the specified COMMON block into a huge data
segment. The format for this option is: +hugecommon=name
+hugecommon
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:
Example 4 % f90 +hugecommon=results pcvals.f90
places the COMMON block named results into a huge data segment. +hugecommonis especially
useful when a program contains several different COMMON blocks that together occupy more
than two gigabytes but individually occupy less than two gigabytes. In this situation, the largest
COMMON blocks could be placed in a huge data segment when the program is compiled by
specifying their names in multiple +hugecommon options.
If a common block is specified as huge in one object file, it must be specified huge in all object
files. If it is not, the program will fail to link.
NOTE: PA2.0W objects cannot be combined with 32-bit object files. 64-bit applications will
only execute on PA8000-based systems.
+hugesizeinstructs the compiler to place COMMON blocks that are
larger than the specified size into a huge data segment. The format for
this option is: +hugesize=n
+hugesize
where n is the size in kilobytes (1024 bytes).
Command-line options 27