HP Fortran v3.1 Release Notes

HP Fortran Release Notes
Previous Fixes
Chapter 1 37
• A new command-line flag— +sharedlibF90 —resolves potential issues with the F90
driver trying to link with the shared version of libF90. See Command-line flags in “New
Features in Version 3.1” on page 4.
•The PACK intrinsic has been corrected to properly handle nonstandard LOGICAL values.
Previously, a segmentation fault would occur if nonstandard LOGICAL values were
encountered by this intrinsic.
• In previous versions of the compiler, the MERGE intrinsic was unimplemented, resulting in
compiler aborts. Instances where this happened included when the compiler encountered
complicated expressions involving derived types or character strings. The MERGE intrinsic
has been corrected so that it properly handles complicated expressions.
• (HP-UX 11.0 only) Fortran has been corrected so that it works in wide mode (64-bit
addressing) when a derived-type selector is used on an array.
•The LBOUND, UBOUND, and SHAPE intrinsics asserted when their result array was
non-contiguous.
• The Fortran compiler previously declared some variables as thread_private when they
were not. The Fortran memory classes have been changed to correct this.
• (HP-UX 11.0 only) In certain situations, Fortran would abort at +O3 +Oparallel.
• In certain situations, Fortran would abort at +O3 +Opal.
• (HP-UX 11.0 only) Using CXperf profiling support option +pal with optimization enabled
caused Fortran to assert.
•Using +autodbl occasionally resulted in an assert.
• (HP-UX 11.0 only) The HP Performance Analysis Tool CXperf can now profile Fortran
applications with empty routines and compiled with +pa. This is a Fortran fix which
corrects the previous problem of a resulting coredump.
• Wrong answers were generated by Fortran at +O3.
• When the code specified loop interchange, the compiler would not honor c$dir
no_loop_transform in certain situations.
• -g +objdebug now works in the same manner as +objdebuf -g so that +objdebug takes
precedence.
• The compiler would occasionally run out of memory at optimization level +O3.
• SELECT CASE statements with REAL*4 ranges/values failed when +autodbl4 used.
• Explicit double precision constants (3.1D4) were corrupted when +autodbl was specified.
•The ADJUSTL intrinsic returned wrong answers when its argument was a parenthesized
character constant.