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
eld Manual—527255-009
A-1
A TNS/E Native Object Files
This appendix contains the following information:
The Object File Format - the types of object files and their content.
Code and Data Sections - the "ordinary" code and data sections that come from
application source code, possibly with additions by the compiler or linker.
Relocation Tables - when code is relocated, who resolves the address and prepares
relocation tables?
Finding Information About Procedures and Subprocedures in Linkfiles - an introduction
to the .procinfo and .procnames sections of linkfiles.
The DWARF Symbol Table - this table contains information used by debuggers and the
Cobol compiler.
Archives - contains an extension of material covered in a previous section of this
manual.
Tools That Work With Object Files - a quick look at which HP NonStop operating
system tools use object files.
The Object File Format
Some of this general information may also be found in Sections One and Two of this
manual, but this appendix provides much more detail.
Basic Properties of Object Files
User versions of TNS/E tools may run in the following places:
•
All TNS/E versions of the HP NonStop operating system, including both the
Guardian and OSS environments.
•
Some TNS/R versions of the HP NonStop operating system, at least in the
Guardian environment.
•
Appropriate versions of the Windows operating system on PC’s.
TNS/E object files only run on TNS/E.
On Guardian and OSS, object files are unstructured files that are “odd unstructured”,
the same as in TNS/R.
On Guardian and OSS, TNS/E object files have the file code 800.
TNS/E object files use the 64-bit version of the ELF file format.
TNS/E object files are big endian. This means that all their data is big endian.