HP Fortran v2.9 for HP-UX 11i v2 Release Note5991-0697

HP Fortran for HP-UX v2.9

Previous Fixes

Chapter 1 43

• -g +objdebug now works in the same manner as +objdebuf -g so that +objdebug takes

precedence.

• The compiler would occasionally run out of memory at optimization level +O3.

• SELECT CASE statements with REAL*4 ranges/values failed when +autodbl4 used.

• Explicit double precision constants (3.0D4) were corrupted when +autodbl was specified.

• The ADJUSTL intrinsic returned wrong answers when its argument was a parenthesized

character constant.

• modulo(x,y) returned incorrect results when -1 < x/y < 0.

• The ES format descriptor printed zero values incorrectly.

• A never-referenced variable name which was also a common block name caused syntax

errors when used in an EQUIVALENCE statement.

• Using 4-byte integer DO loop indices in wide mode (+DA2.0W) incorrectly inhibited a wide

range of optimizations and auto-parallelization.

• Certain uses of variable length character variables with the POINTER attribute caused

intermittent aborts at runtime.

• NAMELIST input of character arrays was not compatible with FORTRAN 77

(non-standard usage of a scalar subscript but multiple values is now accepted).

• NAMELIST READs in wide mode (+DA.0W) sometimes corrupted memory and caused

unpredictable aborts.

• Some character expressions in a SELECT CASE statement were evaluated more than

once.

• SYSTEM_CLOCK sometimes returned an invalid value.

• Short Hollerith initializers (i.e., 1h3) in DATA statements for REAL variables caused an

internal error.

• Using an INTENT(IN) dummy argument in a subsequent initialization expression

sometimes caused an internal error.

• Referencing a character variable via a substring and later as if it were a function caused

an internal error. Now a syntax error is issued.

• Routines which indirectly used the same module many times caused the compilers symbol

table to become corrupted. The compiler now detects and ignores the indirect redundant

USEstatements(ithasalwaysignoreddirectlyvisibleredundantUSEstatements).

• Several internal errors caused by the +DA2.0 flag have been fixed.