HP-UX 11i Version 2 June 2006 Release Notes

Introduction to HP-UX 11i Version 2
HP-UX 11i v2 Compatibility
Chapter 2
31
• signaling via floating point NaNs (Not a Number)
• applications or debuggers that use ptrace, ttrace, and profil system calls
• core dumps for PA-RISC applications that abort
• applications that read the B-bit in the PSW (Process Status Word)
• applications that use maximum virtual memory (because the dynamic translator
itself consumes a small amount of the virtual memory of a process)
• applications that rely on differences between vfork and fork system calls
• the emulation of debugging tools that have architectural dependencies on the
PA-RISC architecture
Recompiling 32-Bit PA-RISC Applications for Native Execution on Integrity
Servers
In nearly all cases, 32-bit PA-RISC applications can be recompiled for native execution
on Integrity servers without source code modifications. This is true because the HP
compilers for Integrity servers support both 32-bit and 64-bit data models. 32-bit
applications use a data model known as ILP32 in which integers, long integers, and
pointers are all 32 bits. 64-bit applications use a data model known as LP64 in which
integers are 32 bits but long integers and pointers are 64 bits. HP compilers for Integrity
servers support both data models.
In the case of a 32-bit PA-RISC application that is being recompiled for native execution
on Integrity servers, the compiler will emit instructions that cause the application to
behave as though it is a 32-bit application executing on a 32-bit architecture even though
the underlying architecture is 64 bits. This is transparent to the application; it has no
awareness that it is actually executing on a 64-bit architecture. It is this feature of the
HP compilers for Integrity servers that allow the vast majority of 32-bit PA-RISC
applications to be recompiled without source code modification for native execution on
the Integrity server architecture.
Help for Independent Software Vendors
Independent Software Vendors (ISVs):
whose HP-UX 11i v1 application meets the criteria for binary compatibility (i.e., not
kernel intrusive, etc.) and fails to function on HP-UX 11i v2 for PA-RISC as it functions
on HP-UX v1
or
whose HP-UX 11i v2 Integrity server native application is limited to the devices
currently virtualized by Integrity VM and fails to function in a virtual machine as it
functions outside of the virtual machine can contact HP through a special support line
(for North America) at 1-800-249-3294 and use option 2, and then option 1. Help is also
available alternatively by sending an e-mail to [e-mail]. When calling this
number or sending an e-mail, identify the problem as a “compatibility failure” and the
support staff will help you with the situation.