The current 32-bit compilation environment is identical to historical Oracle Solaris OS releases with respect to derived types and their sizes. In the 64-bit compilation environment, some changes in derived types are necessary. These changed derived types are highlighted in the tables that follow.
Notice that although the 32-bit and 64-bit compilation environments differ, the same set of headers is used for both, with the appropriate definitions determined by the compilation options. To understand the options available to an application developer, it helps to understand the _ILP32 and _LP64 feature test macros.
The following examples illustrate the use of feature test macros so that the correct definitions are visible, depending on the compilation environment.Example 2 size_t Defined in _LP64
#if defined(_LP64) typedef ulong_t size_t; /* size of something in bytes */ #else typedef uint_t size_t; /* (historical version) */ #endif
When building a 64-bit application with the definition in this example, size_t is a ulong_t, or unsigned long, which is a 64-bit value in the LP64 model. In contrast, when building an 32-bit application, size_t is defined as a uint_t, or unsigned int, a 32-bit value in either in the ILP32 or the LP64 models.Example 3 uid_t Defined in _LP64
#if defined(_LP64) typedef int uid_t; /* UID type */ #else typedef long uid_t; /* (historical version) */ #endif
In either of these examples, the same result would have been obtained had the ILP32 type representation been identical to the LP64 type representation. For example, if in the 32-bit application environment, size_t was changed to an ulong_t, or uid_t was changed to an int, these would still represent 32-bit quantities. However, retaining the historical type representation ensures consistency within 32-bit C and C++ applications, as well as complete binary and source compatibility with prior releases of the Oracle Solaris operating environment.
Figure 6, Table 6, Differences Between Derived Types – General lists the derived types that have changed. When building a 32-bit application, the derived types available to the developer match those in the _ILP32 column. When building a 64-bit application, the derived types match those listed in the _LP64 column. All of these types are defined in <sys/types.h>, with the exception of the wchar_t and wint_t types, which are defined in <wchar.h>.
When reviewing these tables, remember that in the 32-bit environment, int, long, and pointers are 32-bit quantities. In the 64-bit environment, int are 32-bit quantities while long and pointers are 64-bit quantities.
Figure 7, Table 7, Differences Between Derived Types – Large File Specific lists the derived types specific to the Large Files compilation environment. These types are only defined if the feature test macro _LARGEFILE64_SOURCE is defined.
Figure 8, Table 8, Changed Derived Types – FILE_OFFSET_BITS Value lists the changed derived types with respect to the value of _FILE_OFFSET_BITS. You cannot compile an application with both _LP64 defined and _FILE_OFFSET_BITS==32. By default, if _LP64 is defined, _FILE_OFFSET_BITS==64. If _ILP32 is defined, and _FILE_OFFSET_BITS is not defined, then by default, _FILE_OFFSET_BITS==32. These rules are defined in the <sys/feature_tests.h> header file.