HP Fortran v3.1 Release Notes

HP Fortran Release Notes
Previous Fixes
Chapter 1 25
Nested subroutines produced erroneous addresses to break on when the compiler resumed
generating code for the body of the containing routine.
Occasionally, compilation was slower at +O3 than at +O2, apparently due to the
+Oloop_unroll_jam default set to “on.
An assertion occasionally occurred if an indirect call omitted the alternate return entry on
the first call.
WMATMUL at +O0 added special case for a scalar assign guard that looks like an array
assign.
Occasionally, wdb did not find local variables with “info locals” because variable scope was
declared to be a module rather than a routine.
•Computed goto label references were not relocated for the cloned IF region associated
with an OMP PARALLEL IF.
PHSS_29513 (11.22)
There was a compiler assert in the front-end.
The compiler occasionally aborted with CHARACTER, POINTER, and DIMENSION initialized
fields.
An enhancement was made for +DD64 technical applications.
PHSS_29295 (11.22)
Oversubscripting of common array (invalid source) yielded wrong answers at high
optimization levels.
Wrong answers were received at +O3.
There were issues with POINTER arrays.
•Declaring _F90_F_STOP did not return.
SPECcpu2000 code failed to collect flow.data file.
Performance loss of implementation of a matrix multiplication.
There was an internal compiler error with OMP PARALLEL PPRIVATE equivance.
A module declared zero size aborts with +DD64.