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-7
TNS/E object file format
the processor generates a fault to allow software to find and load the missing entry
from a memory-management structure.
TNS/E object file format. This object file format is an amalgam of Intel IA-64 code
architecture and the HP NonStop operating system extensions.
TNS/E object files are categorized into three types of files: linkfiles, loadfiles, and
import libraries. The following are key differences between TNS/R and TNS/E
platforms:
User library. A loadable library; primarily a legacy feature for NonStop systems. For PIC
programs, a user library is a DLL treated as if it were the first library in the
program's libList and therefore is searched first for symbols required by the
program. However, a user library does not appear in the program's libList; instead,
its name is recorded in the program's loadfile as the libname attribute. A program
can be associated with at most one user library; the association can be specified
using the linker at link time or in a later change command, or at run time using the
process creation interfaces. (The /LIB.../ option to the RUN command in TACL
uses these interfaces.)
VHPT. Virtual Hash Page Table: an Itanium® architecture feature that can supply missing
TLB entries without generating faults.
VPROC. The version procedure number used to identify which version of the product you
are using.
Zimpimp file. The internal name of the imp-imp file. Also called the "import library that
represents the implicit DLL's", it is the file that tells which symbols are available in the
set of implicit DLL's, which collectively correspond to what was previously called the
system library. See also Implicit library import library (imp-imp)
.
Platform TNS/R TNS/E
Processor MIPS RISC Itanium
Architecture SGI Intel IA-64
Programming
model
32-bit (ILP32) 32-bit (ILP32)
and in future:
64-bit LP64
Object type ELF and COFF ELF exclusive
Debugging
symbols
Third-Eye DWARF2
Compiler
Backend
SGI w/ HP
extensions
Intel w/ HP
extensions
Linker, PIC ld
eld