HP eld Manual page 249

TNS/E Native Object Files
.liblist Section
In a loadfile, this tells the names of the DLLs that were in the linker command
stream when the linker built this loadfile. In an import library that represents a
single DLL it contains the same information as in that DLL.
.dynsym.gblzd Section
This is a symbol table section, similar to the .dynsym section (see below), but just
for globalized symbols. It may be present in loadfiles and import libraries.
.hash.gblzd Section
This is a hash table section, similar to the .hash section (see below), but for looking
up symbols in the .dynsym.gblzd section.
.hashval.gblzd Section
This is similar to the .hashval section (see below), but providing information about
the symbols in the .dynsym.gblzd section.
.rela.gblzd Section
This is similar to the .rela.dyn section (see below), but for the relocation sites
whose targets are globalized symbols.
.dynstr2 Section
This is a string space that is pointed at from the .dynamic, .liblist, and
.dynsym.gblzd sections.
Stack Unwinding Sections
These contain information for stack unwinding. Note that there are two such
sections in a linkfile (not counting the relocation table section named
.rela.IA_64.unwind), and three such sections in a loadfile.
.rconst Section
This contains application-defined initialized data that does not get modified at
runtime, and does not contain addresses that might need modification when the
loadfile is first brought into memory. This may never be created by a compilation
or assembly, but when the linker sees an input section named .rdata that contains
no relocation sites it renames the section to .rconst.
.plt Section
This section contains import stubs. An import stub is created by the linker in a
loadfile when the linker cannot guarantee that the target of an IP-relative procedure
call is resolved within the same loadfile.
eld Manual—527255-009
A-7
Summary of the Contents of an Object File