Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP Fortran v2.8 for HP-UX 11.0/11i v1 and 11i v2 Release Note*5990-6773* > Chapter 1 HP Fortran v2.8 for HP-UX 11.0/11i v1 and 11i v2

Restrictions in HP Fortran

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

This section lists restrictions you should observe when using the HP Fortran compiler and when using HP Fortran language features in your programs.

+FPI

+FPI will not work when calling any type of runtime libraries or intrinsics.

Object files generated at optimization level 4

Object files generated by the compiler at optimization level 4, called intermediate object files, are intended to be temporary files. These object files contain an intermediate representation of the user code in a format that is designed for advanced optimizations. Therefore, Hewlett-Packard may be required to change the format of these intermediate files in any compiler release or patch. Use of intermediate object files should be limited to the compiler which created them. For the same reason, intermediate object files should not be included into archived libraries that may be used by different versions of the compiler. The compiler will issue an error message and terminate when an incompatible intermediate object file is detected.

+Oparallel_intrinsics

The +Oparallel_intrinsics option links in the parallel version of many of the Fortran intrinsics located in libF90_parallel. However, libF90_parallel for Itanium®-based systems is still only a serial library. It will be parallelized in a future patch.

“OUT OF FREE SPACE” Error

The HP Fortran Programmer’s Reference states that the IOSTAT= and ERR= specifiers return error 913 (OUT OF FREE SPACE) when the I/O library attempts to use more memory than is available. However, these specifiers do not detect all instances of error 913, especially those caused by memory allocation failures in the I/O library.

NODEPCHK ignored

The NODEPCHK directive is sometimes ignored. The symptom was that programs which use the directive would not parallelize as well as expected.

To parallelize your code, use another directive such as loop_parallel. In loops defined with NODEPCHK, we recommend that you not invoke parallelism.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 1979-2003 Hewlett-Packard Development Company, L.P.