Binary Compatibility Issue with Instrumented Code Using PBO or +O4 Optimization

This note pertains to the compilers and linker for HP C, HP aC++, HP C++ (cfront), HP Fortran 77, and HP-UX Linker.

When you compile your source code with the compiler shipped on HP-UX 11.0 Extension Pack, December 1998, without any changes to source code, options, or makefiles, you might create relocatable object files or executables that are no longer backward compatible to an original 11.0 system. This condition will occur if you recompile with PBO (+I compiler or linker option) or the +O4 option. You might create instrumented objects (ISOM) that an 11.0 system does not recognize.

Under these circumstances, one of the following types of error messages will be issued if you attempt to link the objects created using the HP-UX 11.0 Extension Pack compiler on an original 11.0 system.

If you compile with +O3 or +O4, you receive the following message and a stack trace: report error(13-12299-434) to your nearest HP service representative (8911)
If you compile with "+O2 +I", you receive the following message and a stack trace: Backend Assert ** Ucode versions earlier than v.4 no longer supported. (5172)




	NOTE: This code is not backward-compatible with the 11.0 release. Instrumented object files cannot be moved backward.

Binary Compatibility Issue with Instrumented Code Using PBO or +O4 Optimization

Technical documentation

» Table of Contents