eld Manual
Table Of Contents
- eld Manual
- Legal Notices
- Contents
- What’s New in This Manual
- Manual Information
- New and Changed Information
- About This Manual
- Notation Conventions
- 1 Introduction to eld
- 2 eld Input and Output
- 3 Binding of References
- Overview
- Presetting Loadfiles
- To Preset or Not to Preset, and Creation of the LIC
- Handling Unresolved References
- Using User Libraries
- Creating Import Libraries
- Ignoring Optional Libraries
- Merging Symbols Found in Input Linkfiles
- Accepting Multiply-Defined Symbols
- Using the -cross_dll_cleanup option
- Specifying Which Symbols to Export, and Creating the Export Digest
- Public Libraries and DLLs
- The Public Library Registry
- 4 Other eld Processing
- Adjusting Loadfiles: The -alf Option
- Additional rules about -alf
- The -set and -change Options
- eld Functionality for 64-Bit
- Checking the C++ Language Dialect
- Renaming Symbols
- Creating Linker-Defined Symbols
- Updating Or Stripping DWARF Symbol Table Information
- Modifying the Data Sections that Contain Stack Unwinding Information
- Creating the MCB
- Processing of Floating Point Versions and Data Models
- Specification of the Main Entry Point
- Specifying Runtime Search Path Information for DLLs
- Merging Source RTDUs
- 5 Summary of Linker Options
- 6 Output Listings and Error Handling
- A TNS/E Native Object Files
- Glossary
- Index
TNS/E Native Object Files
eld Manual—527255-009
A-9
Summary of the Contents of an Object File
.rdata Section
This contains application-defined initialized data that does not get modified at
runtime (although the initial values may be addresses that need modification when
the loadfile is first brought into memory).
.fptr Section
This section contains official function descriptors. An official function descriptor
contains the address and GP value for a procedure that exists in this loadfile.
Procedure pointers point at official function descriptors. An official function
descriptor is only created for a procedure if the address of that procedure is taken
in the same loadfile, or if the procedure is exported from the loadfile.
.srdata Section
This contains application-defined initialized data that does not get modified at
runtime (although the initial values may be addresses that need modification when
the loadfile is first brought into memory), and that furthermore is “small” data for
which 22-bit GP-relative addressing is used because the compiler or assembler
can guarantee that the target of the reference is in the same loadfile.
.got Section
This is the global offset table, which contains addresses of data items that are
referenced indirectly, as well as the addresses of official function descriptors and
EnterPriv labels. The linker creates entries in the .got section as necessary. The
entries in the .got section are found by 22-bit GP-relative addressing.
.IA_64.pltoff Section
This section contains local function descriptors. A local function descriptor
contains the address and GP value for a procedure that is referenced from this
loadfile. Direct procedure calls (i.e., not involving procedure pointers) use these
local function descriptors. The linker creates entries in the .IA_64.pltoff section as
necessary. The entries in the .IA_64.pltoff section are found by 22-bit GP-relative
addressing.
.sdata Section
This contains application-defined initialized “small” data for which 22-bit GP-relative
addressing is used because the compiler or assembler can guarantee that the
target of the reference is in the same loadfile.
.sbss Section
This contains application-defined uninitialized “small” data for which 22-bit GP-
relative addressing is used because the compiler or assembler can guarantee that
the target of the reference is in the same loadfile. This section occupies no space
in an object file, but rather reserves memory space that is automatica
lly initialized