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

Output Listings and Error Handling
eld Manual—527255-009
6-22
Error Messages
Recovery. None required, because even though the DLLs say they require a specific
type of floating point at runtime, that might not really be true. You might want to look
into this further, though, with people who are familiar with what those DLLs actually do
need.
Cause. You are building a DLL, and it says that it needs the “Tandem” type of floating
point at runtime, but during this link eld is also looking at various other DLLs, and
among those other DLLs eld sees that at least one says that it requires the “IEEE”
version of floating point at runtime.
Effect. Warning (eld produces an output file, but it thinks that you might want to see
this warning about what might go wrong at runtime).
Recovery. If the DLL being built does not actually need the “Tandem” type of floating
point, it would be nicer to use the -set floattype neutral option, to say so. However,
even if this DLL does require the “Tandem” type of floating point at runtime, there isn’t
necessarily a problem here. Even though another DLL says that it requires the “IEEE”
version of floating point, that might not really be true. You might want to look into this
further, though, with people who are familiar with what that other DLL actually does
need.
Cause. You are building a DLL, and it says that it needs the “IEEE” type of floating
point at runtime, but during this link eld is also looking at various other DLLs, and
among those other DLLs eld sees that at least one says that it requires the “Tandem”
version of floating point at runtime.
Effect. Warning (eld produces an output file, but it thinks that you might want to see
this warning about what might go wrong at runtime).
Recovery. If the DLL being built does not actually need the “IEEE” type of floating
point, it would be nicer to use the -set floattype neutral option, to say so. However,
even if this DLL does require the “IEEE” type of floating point at runtime, there isn’t
necessarily a problem here. Even though another DLL says that it requires the
“Tandem” version of floating point, that might not really be true. You might want to look
into this further, though, with people who are familiar with what that other DLL actually
does need.
1144 Floating point type inconsistency. The DLL being
created specifies 'tandem'. DLL <filename> specifies 'ieee'.
1145 Floating point type inconsistency. The DLL being
created specifies 'ieee'. DLL <filename> specifies 'tandem'.
1146 The program being created is floating point type 'ieee'.
DLL <filename> is 'tandem'.










