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
Glossary
eld Manual—527255-009
Glossary-4
Loadfile
Loadfile. hThis term describes the input to the runtime loader and default output of the
linker. This object file may contain name references to symbols that exist in other
loadfiles in the same process. Such references are typically resolved when the
loadfiles are brought into memory by the runtime loader rld . This term is synonymous
with the term "executable" file. An executable object code file is one that is ready for
loading into memory and executing on the computer. Loadfiles are further classified as
executable programs (containing a main routine at which to begin execution of that
program) or executable libraries (supplying routines or variables to multiple programs
or separately loaded libraries). A TNS code file might be both a loadfile and a linkfile.
Native code files are never both. Contrast with Linkfile.
LoadList. A list of all the libraries that must be loaded for a given loadfile to execute. A
loadfile’s loadList includes all the libraries in the given loadfile’s libList plus all the
libraries in those loadfiles’ libLists, and so on. It does not include the implicit libraries.
The loadList order is the sequence in which these loadfiles are to be loaded when they
are not already loaded by a previous operation. The loadList of the program includes
all the loadfiles present in the process, in the order they were loaded.
Loadable Library. A loadfile that offers functions and data to other loadfiles. In this
document, DLLs are such libraries. A library cannot be invoked externally, for
example, by a RUN command; instead, it is invoked by calls or data references
from client loadfiles. In TNS/E, functions and data can also be obtained from the
system library and millicode.
Loader Library. A public library for loading PIC programs and libraries. It works in close
cooperation with the operating system. It is called "rld" when loading a program
and its libraries at process creation time. It also exports a set of functions for
dynamic loading.
Localized. The import-control characteristic of a loadfile that allows it to import symbols
only from the loadfile itself followed by the libraries in its libList, libraries that those
libraries re-export, and from these, any successions of re-exported libraries.
MCB. The Master Control Block. This contains global information such as the product
version number, valid file types, language dialects and floating point types that may be
used.
Millicode library. Low-level library routines. Although separate from it, the millicode can be
considered an adjunct of the system library.
Presetting. This is the process of resolving references to DLLs at linktime.
PIC. This term stands for 'position independent code' and describes a nomenclature
associated with DLLs whereby PIC text contains references do not have to be resolved
at link time. Executable code that need not be modified to run at different virtual
addresses. External reference addresses appear only in a data area that can be
modified by the loader; they do not appear in PIC code. PIC code is even more
position independent than one might imagine from the term; it can be simultaneously