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

HP Fortran for HP-UX v2.9

Previous Fixes

Chapter 160

• IXOR of logical*1 was not supported.

• A new switch, +io77, was added to support E and G format treatment of leading zeros to

match FORTRAN 77 compiler output for easier comparison of prior results.

• +fastallocatable caused errors with allocatable arrays that were SAVEd.

• There was a Compiler Internal Error when a module defined a COMMON block and

USEd another module that also defined the same COMMON block.

PHSS_22290 (10.20) and PHSS_22291 (11.x)

• The compiler failed to correctly handle a constant argument to sizeof.

• EQUIVALENCE statements with shared common were not handled correctly by the

compiler.

PHSS_22112 (10.20) and PHSS_22113 (11.x)

• Some OpenMP directives caused compiler internal errors when used with Modules.

• When multiple load options occurred in a single compile line and the later options were

shorter than the earlier options, incorrect behavior occurred.

•Thezero-basedgetarg solution provided by PHSS_20578 caused incompatibilities for

some customers using shared library calls to getarg.

• FSTREAM intrinsic only returned the lower 32 bits of FILE *fp pointer, causing problems

for applications using wide mode (+DA2.0W).

• Hollerith literals that extended beyond a single line behaved differently in FORTRAN 77

+es than with Fortran with +extend_source.

• Request for closer correspondence of I/O output between FORTRAN 77 and Fortran 90.

PHSS_21787 (10.20) and PHSS_21788 (11.x)

• The use of OpenMP runtime routines not yet available (such as omp_get_thread_num,

omp_set_lock, omp_unset_lock, omp_test_lock) caused an abnormal exit from the

compiler instead of returning an appropriate error message.

• There were instances of a segmentation fault in the Fortran front end after an invalid

alternate return was detected.

•Theuseof+fastallocatable building module occasionally returned an error.

• Previously, there was a problem with SPEC 191.fma3d.

• The compiler aborted when a PARAMETER value was placed in a CHARACTER declaration.