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-15
Predefined Symbols
Note that the sections listed above do not imply that the address of the symbol is in
that section. The value in st_scndx doesn't really matter, because the st_value fi
eld
gives the symbol's value, not its offset within a section. But something needs to be
filled in for the st_shndx fi
eld, and it needs to be a real section, not "absolute", so that
rld and the -alf option of the linker know that it should be updated for rebasing.
Accordingly, the section indices shown above have been chosen. The linker will
always create sections named .text and .data, even if they would be empty, so that
their indices can be used in this way. Note that_unwind_size is absolute. Also, if the
loadfile has no code, and therefore has no .IA_64.unwind section, then the symbol
named _unwind is made absolute, and in this case both _unwind and _unwind_size
have the value 0.
Table A-3. Additional Predefined Symbols Optionally Created By The Linker In
Loadfiles
Name Meaning Value of st_shndx
_BASE_ADDRESS The address of the text
segment.
The index of the .text
section.
_DYNAMIC The address of the .dynamic
section.
The index of the
.dynamic section.
_unwind The start of the .IA_64.unwind
section.
The index of the
.IA_64.unwind
section, or SHN_ABS
(see the explanation
below).
_unwind_size The number of entries in the
.IA_64.unwind section.
SHN_ABS
etext or _etext The end of the text segment. The index of the .text
section.
fdata or _fdata The start of the data (constant)
segment.
The index of the .data
section.
_GLOBAL_OFFSET_TA
BLE
The address of the .got section. The index of the .got
section.
__gp The GP value. The index of the .got
section.
edata or _edata The end of the initialized data,
which is also the start of the
uninitialized data.
The index of the .data
section.
end or _end The end of all the data. The index of the .data
section.