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-6
Summary of the Contents of an Object File
Note that the sections from .got through .sbss are purposely kept together as much as
possible, because they are all referenced with GP-relative addressing. However, when
there are two data segments, the .data section is allowed to intrude among these
sections.
Both the data constant segment and data variable segment can have data that
requires modification by rld when loaded into memory. The difference is that the data
constant segment cannot be modified thereafter, while the data variable segment can.
The following is a brief description of each of the items that can occur in a linkfile or
loadfile. Unless otherwise stated, a section is not required to be present if, based on
its description, it would not contain any useful information for a given object file.
ELF Header
This contains header information for the entire file. It is always found at the start of
an ELF file.
ELF Program Headers
These contain information that summarizes the main parts of the object file
required for loading into memory. Program headers are required in loadfiles and
import libraries.
.tandem_info Section
This contains more information of interest to the operating system. It is required in
loadfiles and import libraries. It also exists in linkfiles because some of its fi
elds
are also meaningful there.
.lic Section
This contains information about the DLLs that were used to preset this loadfile. It
is required in a loadfile, as a placeholder even if the loadfile is not preset.
.dynamic Section
This contains information needed by the runtime loader, such as the addresses of
the .liblist through rela.dyn sections. It is required in loadfiles and import libraries.
.gateway (for a DLL)
DWARF Symbol Table Sections X
.source.rdtu (if present, there are three of them.)
.object.rdtu (if present, there are three of them.)
.shstrtab X
ELF Section Headers X
Table A-2. Contents of a Loadfile or Import Library
Loadfile Contents
GP-
Relative
Import
LIbrary