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

Other eld Processing
eld Manual—527255-009
4-7
Additional rules about -alf
•
GP-relative addressing from the gateways to the text segment, specifically, when
the gateway contains the 64-bit GP-relative address of the procedure for which it is
the gateway.
The way that the -alf option updates all the items listed above depends on the type
of item:
•
If the target of the reference is identified by name, -alf updates the reference
based on that name.
•
If the reference site is one that is filled in by the linker, and -alf only knows that it
needs to be updated by the amount that this DLL was rebased, -alf determines
which segment previously contained the target of the reference and then updates
the reference site by the amount that that segment moved.
eld reports an error if the existing file cannot be opened for reading. It is possible to
specify the -o option to tell the name of the new output file. If the -o option is not
specified then it defaults to the same name as the existing loadfile. Even if the existing
file is a DLL, its DLL name does not influence the output file name. The output file is
created by the same method as described in The Creation of Output Object Files on
page 2-5, including the use of the -temp_o option or the -must_use_oname option.
Here is a complete list of the user options that are allowed with the-alfoption:
-allow_missing_libs
-first_L
-L
-local_libname
-must_use_oname
-must_preset
-no_preset
-no_verbose
-no_version_check
-nostdlib
-o
-obey
-public_registry
-rld_first_L
-rld_L
-stdin
-t -temp_o
-unres_symbols
-verbose
-warn
For further information on -alf see Appendix , How -alf Updates DWARF
for a
discussion of the debug.reloc section of the object file.










