HP Fortran v2.9 for HP-UX 11i v2 Release Note*5991-0697*

HP Fortran for HP-UX v2.9
Previous Fixes
Chapter 1 33
• There sometimes was a segmentation violation during cloning of a vararg routine.
• When compiling a file not in the current directory with +cpp_keep, the filename given in
error and warning messages may be incorrect.
• +Oparallel disables speculative loads in parallel regions.
• Default cpp options were identical between PA and IA; they should be different.
• When using +asm/-S in combination with +P/+Oprofile, +asm/-S were occasionally
ignored.
• There sometimes were incorrect answers with optimizations greater than +O1.
• There was an internal failure in low level optimizer, cm_misc.C.
• The compiler occasionally aborted with OpenMP and the PREFETCH directive.
• Fortran had options to select shared libF90 and libU77 libraries, but no corresponding
option for libIO77.
• The compiler occasionally aborted when +i8 was used with values greater than 2**31.
• The compiler sometimes issued an internal error message when the first argument to an
elemental procedure was not an array.
• The compiler occasionally aborted with an error in the Arith.C routine of the low level
optimizer.
• The compiler sometimes generated inefficient code at +O3 +Oparallel.
• There were wrong answers from generated programs at optimizations greater than +O1
when using -K.
• Wrong answers were given from generated programs at optimization levels greater than
+O2 with or without +Odataprefetch.
• Extensive use of automatic arrays in a subroutine with a very high call count resulted in
poor performance due to using malloc for automatic array allocation.
• There was a segmentation fault compiling incomplete program.
• There was a segmentation fault compiling f90 program with functions returning pointer
to array of derived type containing a private typed object.
• The compiler aborted with santity test failure in DataPrefetch.
• The compiler aborted with +i8 in TMDATE.
• The compiler encountered an internal error in ModSched.C.
• Compiling with +Oparmsoverlap resulted in segmentation fault.