HP-UX Linker and Libraries User's Guide

Table 14 Differences in options between PA-32 and IPF/PA-64 bit modes
DescriptionOption
Specifies incremental loading. IPF applications must use shared libraries instead.-A name
Does parameter type checking. This option is unsupported.-C n
Generates an initial program loader header file. This option is unsupported.-S
Save data and relocation information in temporary files to reduce virtual memory
requirements during linking. This option is unsupported.
-T
Generates an executable with file type DEMAND_MAGIC, EXEC_MAGIC, and SHARE_MAGIC
respectively. These options have no effect and are ignored in IPF (32 bit and 64 bit) and
PA-64.
-q, -Q, -n
Causes the data segment to be placed immediately after the text segment. This option is
accepted but ignored in 64-bit mode. If this option is used because your application data
-N
segment is large, then the option is no longer needed in 64-bit mode. It can be used in
32-bit and IPF applications. If this option is used because your program is used in an
embedded system or other specialized application, consider using mapfile support with
the -k option.
Specifies pathname for compiling I-SOMs to SOMs. This option is unsupported.+cgpathname
In IPF (32-bit and 64-bit), the compiler option +objdebug is the default. When used with
-g, the +objdebugoption leaves debug information in the object files instead of copying
+objdebug mode
it to the executable file at link time, resulting in shorter link times and smaller executables.
The +noobjdebug option can be used to override the +objdebug option and copy all
debug information to the executable file.
In IPF (32-bit and 64-bit), the +srcpos option is the default. The +srcpos option causes
the compiler to generate part of the debug information even when the -g compiler option
+nosrcpos
is not specified. The +srcpos option also causes part of the debug information to be
always copied over to the executable file resulting in larger executables. The +srcpos
option enables users to profile programs using tools like CXperf and HP Caliper, or compiler
options like +I and +P, even in the absence of -g compilation. The linker option
+nosrcpos can be used to override the +srcpos option and strip the associated debug
information during link time. The +nosrcpos option can also be used with -g+objdebug
to fully enforce the +objdebug mode (i.e., leaving the debug information in the object
files).
Table 15 Differences in behavior between PA-32 and IPF/PA-64 bit modes
DescriptionBehavior
In PA-RISC (PA-32 and PA-64) shared libraries are suffixed with .sl. In
IPF (32-bit and 64-bit), the shared libraries are suffixed with .so. For
compatibility, the IPF linker also supports the .sl suffix.
Share library suffix
Specified by using the HP_SHLIB_VERSION pragma (C and aC++) or
SHLIB_VERSION directive (Fortran90). In PA-32 mode, the linker lets
Intra-library versioning
you version your library by object files. IPF or PA-64 applications must
use SVR4 library-level versioning instead.
Code and data cannot share the same namespace in IPF mode. You must
rename the conflicting symbols.
Duplicate code and data symbols
These options are unsupported.All internal and undocumented linker options
Table 16 Differences in Toolset between PA-32 and IPF/PA-64 bit modes
DescriptionToolset
The odump tool that displays information about a SOM object file is not supported.odump
Link-time Differences Between SOM (PA32) and ELF (PA64 and Itanium) 81