Table 14 Differences in options between
Option | Description |
|
|
Specifies incremental loading. IPF applications must use shared libraries instead. | |
|
|
Does parameter type checking. This option is unsupported. | |
|
|
Generates an initial program loader header file. This option is unsupported. | |
|
|
Save data and relocation information in temporary files to reduce virtual memory | |
| requirements during linking. This option is unsupported. |
|
|
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 |
| |
|
|
Causes the data segment to be placed immediately after the text segment. This option is | |
| accepted but ignored in |
| segment is large, then the option is no longer needed in |
| |
| embedded system or other specialized application, consider using mapfile support with |
| the |
|
|
+cgpathname | Specifies pathname for compiling |
|
|
+objdebug mode | In IPF |
| |
| 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. |
|
|
+nosrcpos | In IPF |
| the compiler to generate part of the debug information even when the |
| 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
Table 15 Differences in behavior between
Behavior | Description |
Share library suffix | In |
| IPF |
| compatibility, the IPF linker also supports the .sl suffix. |
|
|
Specified by using the HP_SHLIB_VERSION pragma (C and aC++) or | |
| SHLIB_VERSION directive (Fortran90). In |
| you version your library by object files. IPF or |
| use SVR4 |
|
|
Duplicate code and data symbols | Code and data cannot share the same namespace in IPF mode. You must |
| rename the conflicting symbols. |
All internal and undocumented linker options These options are unsupported.
Table 16 Differences in Toolset between
Toolset | Description |
|
|
odump | The odump tool that displays information about a SOM object file is not supported. |
|
|