HP Fortran v3.1 Release Notes
HP Fortran Release Notes
Previous Fixes
Chapter 124
• There was an occasional compiler abort at +O3.
• Wrong answers were given at +O2 and above for MATMUL(TRANSPOSE(S),S).
• When using +O2, the compiler generated code which resulted in a memory core dump.
•There was a dataval name issue.
•There was a rsqrt performance issue.
• The allocated memory size of common block differed by the way of declaration.
• There was an occasional middle end assertion.
PHSS_29663 (11.23)
• Out-of-bounds access to an array stored in a common block yielded wrong answers at high
optimization levels.
• Wrong answers were occasionally received at +O3.
• There was an issue with POINTER arrays.
• Occasionally, declare_F90_F_STOP did not return.
• SPECcpu2000 occasionally failed to collect the flow.data file.
• There was a performance loss of implementation of a matrix multiplication.
• Occasionally, there was a compiler internal error with OMP PARALLEL PRIVATE
equivalence variables.
• A module with a declared zero size would abort with +DD64.
• The compiler occasionally asserted in FE.
• There was a compiler abort with CHARACTER, POINTER, and DIMENSION initialized fields.
Fixes not present in prior patch releases
• There was an issue with math inlining suppression for outlined parallel/workshare
regions.
• There was an HLO assertion failure at +O3.
• When an array index contained a variable with type qualifier, compiling at +O3 +DD64
gave an assert.
• Two array declarations such as integer ar(100) and integer br(100) produced two
unique array declarations, when only one was needed.