HP Fortran v3.1 Release Notes

HP Fortran Release Notes
Previous Fixes
Chapter 1 29
• The compiler occasionally aborted when compiling with both the +Onoinline and
+Oprofile options.
• The compiler aborted when a parameter was equivalenced to a local variable.
• There was an internal failure in low-level optimizer, file SchedDriver.C.
• Wrong answers with +O2 +DSitanium2.
• There was a memory leak when a save statement was used with an automatically
allocated array.
• Wrong answers were generated when passing complex pointers at +O2 optimization.
• There was a performance problem due to loss of loop unrolling.
• The compiler occasionally aborted when trying to initialize a pointer field of a derived
type
PHSS_27073
• Inlined routines containing static (or Fortran SAVE) variables were giving wrong answers
when compiled with +Oparallel or +Oopenmp.
• Wrong answers were given from the code within OpenMP locks.
• The compiler aborted during compilation of rshift.
• The compiler issued an error that a dummy argument of a private procedure could not
have a type that was private.
• There was occasional poor performance with multiple memory moves on some allocatable
array types.
• The compiler occasionally aborted when named parameters were used in some calls.
PHSS_26864
•The SIGXCPU signal did not abort programs that had the UNIX95 environment variable set
when the programs were linked.
• The compiler generated an error message for read(f(),*) when f was a character
function.
• The compiler generated an error message for a labelled ENDDO statement.
• Traceback information did not always output when the compiler aborted.
• The compiler generated an error when a statement function was used for a character
declared with a parameter.