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-2
Export.
Export. To provide a symbol definition for use by other loadfiles. A loadfile offers for export
a symbol definition for use by other loadfiles that need a data item or function
having that symbolic name.
Gateway. For every callable function there is a gateway; all calls to the function jump first to
the gateway, which effects the transition to privileged state if the caller is not
already privileged. There are two types of gateway pages, those that promote to
kernel and those that promote to executive level.
Gblzd. globalized [symbol]
Globalized import. The import-control characteristic of a loadfile that allows it to import
symbols from any loadfile in the loadList of the program with which it is loaded.
When those loadfiles offer multiple definitions of the same symbol, those loadfiles
are searched in loadList sequence and the first definition found takes precedence.
See also searchList.
Globalized symbol. An exported symbol generated by the C++ compiler that may have
multiple definitions, of which the linker and loader must assure only one is used
throughout the process.
Hybrid file. This term describes a 'pseudo-DLL' that contains non-PIC text to allow a PIC
process to call (as inputs) when building or relinking a program or DLL file. Hybrids do
not exist in TNS/E.
Implicit library. A library supplied by HP that is available in the read-only and execute-only
globally mapped address space shared by all processes without being specified to the
linker or loader. The public libraries on TNS/E that replace System Code, System
Library, and millicode. These libraries are called implicit because every loadfile is
implicitly a user of them. Contrast with public DLLs, which are explicit because a
loadfile explicitly asks to use a public DLL, although it does not specify where to find
the public DLL. See also System library. and Public Libraries.
Implicit library import library (imp-imp). An import library that can be used by the Linker
as a proxy for a set of implicit libraries. See Import library and Zimpimp file.
Import. To refer to a symbol definition from another loadfile. A loadfile imports a symbol
definition when it needs a data item or function having that symbolic name.
Import control. The characteristic of a loadfile that determines from which other loadfiles it
can import symbol definitions. The programmer sets a loadfile’s import control at link
time. That import control can be localized, globalized, or semiglobalized. A loadfile’s
import control governs the way the linker and loader construct that loadfile’s searchList
and affects the search only for symbols required by that loadfile.
Import library. This term describes one type of a loadfile whereby only enough parts of the
file are contained therein to allow the linker to resolve references, but not enough to
expose its source code; i.e., exports the symbols of the DLL . It is a file that can be
used by the Linker as a proxy for one or more DLLs, but that cannot actually be loaded










