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-10
Summary of the Contents of an Object File
to zero. The object file design supports such sections, although compilers might
not use them.
.bss Section
This contains application-defined uninitialized data, but this section doesn’t have
the restriction that makes it possible to put data into the .sbss section. It occupies
no space in an object file, but rather reserves memory space that is automatically
initialized to zero. The object file design supports such sections, although
compilers might not use them. The linker allocates .bss sections in loadfiles to
contain what the compiler called common data.
.rela.x Sections
These sections describe relocation sites within linkfiles. Relocation sites can be
within code or data sections, including unwind function sections, the .procinfo
section, and the DWARF sections. A .rela.x section is required in a linkfile for each
section named .x that has relocation sites. For example, rela.data describes the
relocation sites in the .data section.
.symtab Section
This is the ELF symbol table. It is required in linkfiles. It contains information
about symbols whose names are meaningful to the linker.
.strtab Section
This is a string space that is pointed at from the .symtab section. It is required in
linkfiles.
.procinfo Section
This section provides information about procedures and subprocedures.
.procnames Section
This is a string space pointed at by the .procinfo section.
DWARF Symbol Table Sections
These sections contain information for the debugger and for the COBOL compiler.
There are several sections that collectively form the DWARF symbol table.
Source RTDU Sections
These are sections that represent source RTDU’s, which are part of the SQL/MP
implementation. These can exist only in linkfiles and programs. In a linkfile that is
created by compiling a source file with embedded SQL/MP, the set of source
RTDU’s is represented by three sections. In a program, the set of source RTDU’s
is also represented by three sections, although not with the same section names
as in a linkfile.