HP Fortran Programmer's Guide (September 2007)

Migrating to HP Fortran
Migration issues
Chapter 10224
Refer to the HP Fortran Programmer's Reference for information about all of the HP Fortran
intrinsics and the libU77 routines.
Command-line option issues
Command-line options can become a migration issue in two ways:
• When you compile a program with the HP Fortran compiler, using an f77 command line.
If the command line contains an unsupported f77 option, f90 will flag the option with an
error message.
Table 10-5 lists the f77 and f90 that have the same functionality but different names. See
Table on page 215 for a list of f77 options that are not supported by f90 and Table on
page 215 for a list of f77 options that have been replaced by f90 options.
• When you execute a program that consists of a mix of object files that have been created
by f77 and f90. The problem here is that, although the object files may have been
successfully linked, they may not be compatible. If they were incompatible, the resulting
executable could behave unexpectedly or produce wrong results. Migration problems
caused by incompatible object files are unusual but more difficult to detect and are
discussed in the next section.
GETENV LOC TIME
Table 10-5 f77 options supported by f90
f77
option f90 option function
-C +check=all Perform runtime subscript checking
-G +gprof Prepare for profiling with gprof
-K +save Use static storage for locals instead of stack
-N +noshared Mark linker output unshared
-n +shared Mark linker output shared
-p +prof Prepare for profiling with prof
-Q +nodemand_load Do not mark linker output demand load
-q +demand_load Mark linker output demand load
Table 10-4 Conflicting intrinsics and libU77 routine names (Continued)