Jump to content
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
HP.com home

Transition Impacts

HP-UX Software Transition Kit
» 

DSPP Home

» HP STK home
HP-UX STK
» Home
» Overview
» Tools
» Documentation
» Transition impacts
» Identifier types
» Impact list
» Qualifying on HP-UX
» Porting to HP-UX
» FAQ
» Glossary
» Help
» Send us feedback
Site maps
» HP-UX STK
» DSPP
Content starts here

64-bit API impacts summary

 

64-Bit API Impacts Summary


There are three types of code changes needed to create a 64-bit version of your software from your 32-bit clean source code:

  • convert from a 32-bit data model to a 64-bit data model
  • use the new 64-bit APIs
  • incorporate 64-bit features

32-bit and 64-bit UNIX computing use different data models. The data model used in 32-bit UNIX computing is called ILP32, meaning that integers, longs and pointers are all 32-bit data types. The data model used in 64-bit UNIX computing is called LP64, meaning that longs and pointers are 64-bit data types while integers remain as 32-bit data types. Some existing C and C++ code assumes that integers, longs and pointers are the same size. Because these assumptions are not true in LP64, some executables have defects when they are compiled for 64-bits.

Note: To include only 64-bit impacts when running the scansummary and scandetail tools, use the option:
  +C 64
To exclude these impacts, use the option:
  -C 64

For more information on filtering output in reports, see Customizing Your Scan.

For more information

 
»  List of 64-Bit Impacts
»  How to Write a 64-Bit Clean IO Driver for HP-UX (.pdf)
»  Transitioning C and aC++ Programs to the 64-Bit Data Model
»  HP-UX 64-Bit Porting Concepts
»  Interoperability of 32- and 64-Bit Applications on 64-Bit HP-UX
»  HP-UX 64-Bit Compiler and Linker Changes
Printable version
Privacy statement Using this site means you accept its terms Feedback to DSPP
© 2007 Hewlett-Packard Development Company, L.P.