1 .\" Copyright (c) 1999 Jeroen Ruigrok van der Werven
2 .\" All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
13 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
14 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
15 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
16 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
17 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
18 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
19 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
20 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
21 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
22 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32 .Nd format of ELF executable binary files
38 defines the format of ELF executable binary files.
39 Amongst these files are
40 normal executable files, relocatable object files, core files and shared
43 An executable file using the ELF file format consists of an ELF header,
44 followed by a program header table or a section header table, or both.
45 The ELF header is always at offset zero of the file.
47 table and the section header table's offset in the file are defined in the
49 The two tables describe the rest of the particularities of
52 Applications which wish to process ELF binary files for their native
53 architecture only should include
56 These applications should need to refer to
57 all the types and structures by their generic names
61 Applications written this way can be compiled on any architecture,
62 regardless whether the host is 32-bit or 64-bit.
64 Should an application need to process ELF files of an unknown
65 architecture then the application needs to include both
71 Furthermore, all types and structures need to be identified by either
75 The macros need to be identified by
80 Whatever the system's architecture is, it will always include
83 .In sys/elf_generic.h .
85 These header files describe the above mentioned headers as C structures
86 and also include structures for dynamic sections, relocation sections and
89 The following types are being used for 32-bit architectures:
90 .Bd -literal -offset indent
91 Elf32_Addr Unsigned 32-bit program address
92 Elf32_Half Unsigned 16-bit field
93 Elf32_Lword Unsigned 64-bit field
94 Elf32_Off Unsigned 32-bit file offset
95 Elf32_Sword Signed 32-bit field or integer
96 Elf32_Word Unsigned 32-bit field or integer
99 For 64-bit architectures we have the following types:
100 .Bd -literal -offset indent
101 Elf64_Addr Unsigned 64-bit program address
102 Elf64_Half Unsigned 16-bit field
103 Elf64_Lword Unsigned 64-bit field
104 Elf64_Off Unsigned 64-bit file offset
105 Elf64_Sword Signed 32-bit field
106 Elf64_Sxword Signed 64-bit field or integer
107 Elf64_Word Unsigned 32-bit field
108 Elf64_Xword Unsigned 64-bit field or integer
111 All data structures that the file format defines follow the
113 size and alignment guidelines for the relevant class.
115 data structures contain explicit padding to ensure 4-byte alignment
116 for 4-byte objects, to force structure sizes to a multiple of 4, etc.
118 The ELF header is described by the type Elf32_Ehdr or Elf64_Ehdr:
119 .Bd -literal -offset indent
121 unsigned char e_ident[EI_NIDENT];
123 Elf32_Half e_machine;
124 Elf32_Word e_version;
130 Elf32_Half e_phentsize;
132 Elf32_Half e_shentsize;
134 Elf32_Half e_shstrndx;
137 .Bd -literal -offset indent
139 unsigned char e_ident[EI_NIDENT];
141 Elf64_Half e_machine;
142 Elf64_Word e_version;
148 Elf64_Half e_phentsize;
150 Elf64_Half e_shentsize;
152 Elf64_Half e_shstrndx;
156 The fields have the following meanings:
158 .Bl -tag -width "e_phentsize" -compact -offset indent
160 This array of bytes specifies to interpret the file,
161 independent of the processor or the file's remaining contents.
162 Within this array everything is named by macros, which start with
165 and may contain values which start with the prefix
167 The following macros are defined:
169 .Bl -tag -width "EI_ABIVERSION" -compact
171 The first byte of the magic number.
172 It must be filled with
175 The second byte of the magic number.
176 It must be filled with
179 The third byte of the magic number.
180 It must be filled with
183 The fourth byte of the magic number.
184 It must be filled with
187 The fifth byte identifies the architecture for this binary:
189 .Bl -tag -width "ELFCLASSNONE" -compact
191 This class is invalid.
193 This defines the 32-bit architecture.
194 It supports machines with files
195 and virtual address spaces up to 4 Gigabytes.
197 This defines the 64-bit architecture.
200 The sixth byte specifies the data encoding of the processor-specific
202 Currently these encodings are supported:
204 .Bl -tag -width "ELFDATA2LSB" -compact
208 Two's complement, little-endian.
210 Two's complement, big-endian.
213 The version number of the ELF specification:
215 .Bl -tag -width "EV_CURRENT" -compact
222 This byte identifies the operating system
223 and ABI to which the object is targeted.
224 Some fields in other ELF structures have flags
225 and values that have platform specific meanings;
226 the interpretation of those fields is determined by the value of this byte.
227 The following values are currently defined:
229 .Bl -tag -width "ELFOSABI_STANDALONE" -compact
233 HP-UX operating system ABI.
234 .It Dv ELFOSABI_NETBSD
236 operating system ABI.
237 .It Dv ELFOSABI_LINUX
238 GNU/Linux operating system ABI.
240 GNU/Hurd operating system ABI.
241 .It Dv ELFOSABI_86OPEN
242 86Open Common IA32 ABI.
243 .It Dv ELFOSABI_SOLARIS
244 Solaris operating system ABI.
245 .It Dv ELFOSABI_MONTEREY
246 Monterey project ABI.
248 IRIX operating system ABI.
249 .It Dv ELFOSABI_FREEBSD
251 operating system ABI.
252 .It Dv ELFOSABI_TRU64
253 TRU64 UNIX operating system ABI.
255 ARM architecture ABI.
256 .It Dv ELFOSABI_STANDALONE
257 Standalone (embedded) ABI.
260 This byte identifies the version of the ABI
261 to which the object is targeted.
262 This field is used to distinguish among incompatible versions of an ABI.
263 The interpretation of this version number
264 is dependent on the ABI identified by the EI_OSABI field.
265 Applications conforming to this specification use the value 0.
268 These bytes are reserved and set to zero.
270 which read them should ignore them.
271 The value for EI_PAD will change in
272 the future if currently unused bytes are given meanings.
274 Start of architecture identification.
276 The size of the e_ident array.
280 This member of the structure identifies the object file type:
282 .Bl -tag -width "ET_NONE" -compact
296 This member specifies the required architecture for an individual file:
298 .Bl -tag -width "EM_MIPS_RS4_BE" -compact
304 Sun Microsystems SPARC.
316 MIPS RS3000 (big-endian only).
317 .It Dv EM_MIPS_RS4_BE
318 MIPS RS4000 (big-endian only).
320 SPARC v9 64-bit unofficial.
330 This member identifies the file version:
332 .Bl -tag -width "EV_CURRENT" -compact
339 This member gives the virtual address to which the system first transfers
340 control, thus starting the process.
341 If the file has no associated entry
342 point, this member holds zero.
344 This member holds the program header table's file offset in bytes.
346 the file has no program header table, this member holds zero.
348 This member holds the section header table's file offset in bytes.
350 file has no section header table this member holds zero.
352 This member holds processor-specific flags associated with the file.
354 names take the form EF_`machine_flag'.
355 Currently no flags have been defined.
357 This member holds the ELF header's size in bytes.
359 This member holds the size in bytes of one entry in the file's program header
360 table; all entries are the same size.
362 This member holds the number of entries in the program header
364 If the file is using extended program header numbering, then the
366 member will contain the value
368 and the actual number of program header table entries will be stored
371 member of the section header at index
375 and the number of program header table entries gives the program
376 header table's size in bytes.
377 If a file has no program header,
379 holds the value zero.
381 This member holds a sections header's size in bytes.
382 A section header is one
383 entry in the section header table; all entries are the same size.
385 This member holds the number of entries in the section header table.
386 If the file is using extended section numbering, then the
388 member will be zero and the actual section number will be stored in the
390 member of the section header at index
392 If a file has no section header table, both the
396 fields of the ELF header will be zero.
399 and the number of sections in the file gives the section header
400 table's size in bytes.
402 This member holds the section header table index of the entry associated
403 with the section name string table.
404 If extended section numbering is being used, this field will hold the
407 and the actual section header table index will be present in the
409 field of the section header entry at index
411 If the file has no section name string
412 table, this member holds the value
416 An executable or shared object file's program header table is an array of
417 structures, each describing a segment or other information the system needs
418 to prepare the program for execution.
423 Program headers are meaningful only for executable and shared object files.
424 A file specifies its own program header size with the ELF header's
429 As with the Elf executable header, the program header
430 also has different versions depending on the architecture:
431 .Bd -literal -offset indent
443 .Bd -literal -offset indent
450 Elf64_Xword p_filesz;
456 The main difference between the 32-bit and the 64-bit program header lies
457 only in the location of a
459 member in the total struct.
461 .Bl -tag -width "p_offset" -compact -offset indent
463 This member of the Phdr struct tells what kind of segment this array
464 element describes or how to interpret the array element's information.
466 .Bl -tag -width "PT_DYNAMIC" -compact
468 The array element is unused and the other members' values are undefined.
469 This lets the program header have ignored entries.
471 The array element specifies a loadable segment, described by
475 The bytes from the file are mapped to the beginning of the memory
477 If the segment's memory size
479 is larger than the file size
483 bytes are defined to hold the value 0 and to follow the segment's
485 The file size may not be larger than the memory size.
486 Loadable segment entries in the program header table appear in ascending
491 The array element specifies dynamic linking information.
493 The array element specifies the location and size of a null-terminated
494 path name to invoke as an interpreter.
495 This segment type is meaningful
496 only for executable files (though it may occur for shared objects).
498 it may not occur more than once in a file.
499 If it is present it must precede
500 any loadable segment entry.
502 The array element specifies the location and size for auxiliary information.
504 This segment type is reserved but has unspecified semantics.
506 contain an array element of this type do not conform to the ABI.
508 The array element, if present, specifies the location and size of the program
509 header table itself, both in the file and in the memory image of the program.
510 This segment type may not occur more than once in a file.
512 only occur if the program header table is part of the memory image of the
514 If it is present it must precede any loadable segment entry.
516 This value up to and including
518 are reserved for processor-specific semantics.
520 This value down to and including
522 are reserved for processor-specific semantics.
526 This member holds the offset from the beginning of the file at which
527 the first byte of the segment resides.
529 This member holds the virtual address at which the first byte of the
530 segment resides in memory.
532 On systems for which physical addressing is relevant, this member is
533 reserved for the segment's physical address.
537 not used and must be zero.
539 This member holds the number of bytes in the file image of the segment.
542 This member holds the number of bytes in the memory image of the segment.
545 This member holds flags relevant to the segment:
547 .Bl -tag -width "PF_X" -compact
549 An executable segment.
556 A text segment commonly has the flags
560 A data segment commonly has
566 This member holds the value to which the segments are aligned in memory
568 Loadable process segments must have congruent values for
572 modulo the page size.
573 Values of zero and one mean no alignment is required.
576 should be a positive, integral power of two, and
584 An file's section header table lets one locate all the file's sections.
586 section header table is an array of Elf32_Shdr or Elf64_Shdr structures.
590 member gives the byte offset from the beginning of the file to the section
593 holds the number of entries the section header table contains.
595 holds the size in bytes of each entry.
597 A section header table index is a subscript into this array.
599 header table indices are reserved.
600 An object file does not have sections for
601 these special indices:
603 .Bl -tag -width "SHN_LORESERVE" -compact
605 This value marks an undefined, missing, irrelevant, or otherwise meaningless
607 For example, a symbol
609 relative to section number
611 is an undefined symbol.
613 This value specifies the lower bound of the range of reserved indices.
615 This value up to and including
617 are reserved for processor-specific semantics.
619 This value down to and including
621 are reserved for processor-specific semantics.
623 This value specifies absolute values for the corresponding reference.
625 example, symbols defined relative to section number
627 have absolute values and are not affected by relocation.
629 Symbols defined relative to this section are common symbols, such as FORTRAN
630 COMMON or unallocated C external variables.
632 This value specifies the upper bound of the range of reserved indices.
634 system reserves indices between
639 The section header table does not contain entries for the
643 The section header has the following structure:
644 .Bd -literal -offset indent
654 Elf32_Word sh_addralign;
655 Elf32_Word sh_entsize;
658 .Bd -literal -offset indent
662 Elf64_Xword sh_flags;
668 Elf64_Xword sh_addralign;
669 Elf64_Xword sh_entsize;
673 .Bl -tag -width "sh_addralign" -compact
675 This member specifies the name of the section.
676 Its value is an index
677 into the section header string table section, giving the location of
678 a null-terminated string.
680 This member categorizes the section's contents and semantics.
682 .Bl -tag -width "SHT_PROGBITS" -compact
684 This value marks the section header as inactive.
686 have an associated section.
687 Other members of the section header
688 have undefined values.
690 The section holds information defined by the program, whose
691 format and meaning are determined solely by the program.
693 This section holds a symbol table.
696 provides symbols for link editing, though it may also be used
698 As a complete symbol table, it may contain
699 many symbols unnecessary for dynamic linking.
705 This section holds a string table.
706 An object file may have multiple
707 string table sections.
709 This section holds relocation entries with explicit addends, such
712 for the 32-bit class of object files.
713 An object may have multiple
716 This section holds a symbol hash table.
717 All object participating in
718 dynamic linking must contain a symbol hash table.
720 have only one hash table.
722 This section holds information for dynamic linking.
724 have only one dynamic section.
726 This section holds information that marks the file in some way.
728 A section of this type occupies no space in the file but otherwise
731 Although this section contains no bytes, the
733 member contains the conceptual file offset.
735 This section holds relocation offsets without explicit addends, such
738 for the 32-bit class of object files.
739 An object file may have multiple
742 This section is reserved but has unspecified semantics.
744 This section holds a minimal set of dynamic linking symbols.
746 object file can also contain a
750 This value up to and including
752 are reserved for processor-specific semantics.
754 This value down to and including
756 are reserved for processor-specific semantics.
758 This value specifies the lower bound of the range of indices reserved for
759 application programs.
761 This value specifies the upper bound of the range of indices reserved for
762 application programs.
763 Section types between
767 may be used by the application, without conflicting with current or future
768 system-defined section types.
772 Sections support one-bit flags that describe miscellaneous attributes.
773 If a flag bit is set in
778 Otherwise, the attribute is
781 Undefined attributes are set to zero.
783 .Bl -tag -width "SHF_EXECINSTR" -compact
785 This section contains data that should be writable during process
788 The section occupies memory during process execution.
790 sections do not reside in the memory image of an object file.
792 attribute is off for those sections.
794 The section contains executable machine instructions.
796 All bits included in this mask are reserved for processor-specific
801 If the section will appear in the memory image of a process, this member
802 holds the address at which the section's first byte should reside.
803 Otherwise, the member contains zero.
805 This member's value holds the byte offset from the beginning of the file
806 to the first byte in the section.
809 occupies no space in the file, and its
811 member locates the conceptual placement in the file.
813 This member holds the section's size in bytes.
814 Unless the section type
822 may have a non-zero size, but it occupies no space in the file.
824 This member holds a section header table index link, whose interpretation
825 depends on the section type.
827 This member holds extra information, whose interpretation depends on the
830 Some sections have address alignment constraints.
832 doubleword, the system must ensure doubleword alignment for the entire
834 That is, the value of
836 must be congruent to zero, modulo the value of
838 Only zero and positive integral powers of two are allowed.
840 or one mean the section has no alignment constraints.
842 Some sections hold a table of fixed-sized entries, such as a symbol table.
843 For such a section, this member gives the size in bytes for each entry.
844 This member contains zero if the section does not hold a table of
848 Various sections hold program and control information:
849 .Bl -tag -width ".shstrtab" -compact
851 (Block Started by Symbol)
852 This section holds uninitialized data that contributes to the program's
854 By definition, the system initializes the data with zeros
855 when the program begins to run.
856 This section is of type
858 The attributes types are
863 This section holds version control information.
864 This section is of type
866 No attribute types are used.
868 This section holds initialized data that contribute to the program's
870 This section is of type
872 The attribute types are
877 This section holds initialized data that contribute to the program's
879 This section is of type
881 The attribute types are
886 This section holds information for symbolic debugging.
889 This section is of type
891 No attribute types are used.
893 This section holds dynamic linking information.
894 The section's attributes
900 bit is set is processor-specific.
901 This section is of type
903 See the attributes above.
905 This section holds strings needed for dynamic linking, most commonly
906 the strings that represent the names associated with symbol table entries.
907 This section is of type
909 The attribute type used is
912 This section holds the dynamic linking symbol table.
913 This section is of type
915 The attribute used is
918 This section holds executable instructions that contribute to the process
920 When a program exits normally the system arranges to
921 execute the code in this section.
922 This section is of type
924 The attributes used are
929 This section holds the global offset table.
930 This section is of type
932 The attributes are processor-specific.
934 This section holds a symbol hash table.
935 This section is of type
937 The attribute used is
940 This section holds executable instructions that contribute to the process
942 When a program starts to run the system arranges to
943 execute the code in this section before calling the main program entry point.
944 This section is of type
946 The attributes used are
951 This section holds the pathname of a program interpreter.
953 a loadable segment that includes the section, the section's attributes will
957 Otherwise, that bit will be off.
958 This section is of type
961 This section holds line number information for symbolic debugging, which
962 describes the correspondence between the program source and the machine code.
963 The contents are unspecified.
964 This section is of type
966 No attribute types are used.
968 This section holds information in the
970 format described below.
971 This section is of type
973 No attribute types are used.
975 This section holds the procedure linkage table.
976 This section is of type
978 The attributes are processor-specific.
980 This section holds relocation information as described below.
982 has a loadable segment that includes relocation, the section's attributes
986 Otherwise the bit will be off.
989 is supplied by the section to which the relocations apply.
993 normally would have the name
995 This section is of type
998 This section holds relocation information as described below.
1000 has a loadable segment that includes relocation, the section's attributes
1004 Otherwise the bit will be off.
1007 is supplied by the section to which the relocations apply.
1011 normally would have the name
1013 This section is of type
1016 This section holds read-only data that typically contributes to a
1017 non-writable segment in the process image.
1018 This section is of type
1020 The attribute used is
1023 This section hold read-only data that typically contributes to a
1024 non-writable segment in the process image.
1025 This section is of type
1027 The attribute used is
1030 This section holds section names.
1031 This section is of type
1033 No attribute types are used.
1035 This section holds strings, most commonly the strings that represent the
1036 names associated with symbol table entries.
1037 If the file has a loadable
1038 segment that includes the symbol string table, the section's attributes
1042 Otherwise the bit will be off.
1043 This section is of type
1046 This section holds a symbol table.
1047 If the file has a loadable segment
1048 that includes the symbol table, the section's attributes will include
1052 Otherwise the bit will be off.
1053 This section is of type
1056 This section holds the
1058 or executable instructions, of a program.
1059 This section is of type
1061 The attributes used are
1066 This section holds information about Java classes that must
1069 This section holds information used for C++ exception-handling.
1072 String table sections hold null-terminated character sequences, commonly
1074 The object file uses these strings to represent symbol
1076 One references a string as an index into the string
1078 The first byte, which is index zero, is defined to hold
1080 Similarly, a string table's last byte is defined to
1081 hold a null character, ensuring null termination for all strings.
1083 An object file's symbol table holds information needed to locate and
1084 relocate a program's symbolic definitions and references.
1086 index is a subscript into this array.
1087 .Bd -literal -offset indent
1090 Elf32_Addr st_value;
1092 unsigned char st_info;
1093 unsigned char st_other;
1094 Elf32_Half st_shndx;
1097 .Bd -literal -offset indent
1100 unsigned char st_info;
1101 unsigned char st_other;
1102 Elf64_Half st_shndx;
1103 Elf64_Addr st_value;
1104 Elf64_Xword st_size;
1108 .Bl -tag -width "st_value" -compact
1110 This member holds an index into the object file's symbol string table,
1111 which holds character representations of the symbol names.
1113 is non-zero, it represents a string table index that gives the symbol
1115 Otherwise, the symbol table has no name.
1117 This member gives the value of the associated symbol.
1119 Many symbols have associated sizes.
1120 This member holds zero if the symbol
1121 has no size or an unknown size.
1123 This member specifies the symbol's type and binding attributes:
1125 .Bl -tag -width "STT_SECTION" -compact
1127 The symbol's type is not defined.
1129 The symbol is associated with a data object.
1131 The symbol is associated with a function or other executable code.
1133 The symbol is associated with a section.
1134 Symbol table entries of
1135 this type exist primarily for relocation and normally have
1139 By convention the symbol's name gives the name of the source file
1140 associated with the object file.
1143 bindings, its section index is
1145 and it precedes the other
1147 symbols of the file, if it is present.
1149 This value up to and including
1151 are reserved for processor-specific semantics.
1153 This value down to and including
1155 are reserved for processor-specific semantics.
1158 .Bl -tag -width "STB_GLOBAL" -compact
1160 Local symbols are not visible outside the object file containing their
1162 Local symbols of the same name may exist in multiple file
1163 without interfering with each other.
1165 Global symbols are visible to all object files being combined.
1167 definition of a global symbol will satisfy another file's undefined
1168 reference to the same symbol.
1170 Weak symbols resemble global symbols, but their definitions have lower
1173 This value up to and including
1175 are reserved for processor-specific semantics.
1177 This value down to and including
1179 are reserved for processor-specific semantics.
1181 There are macros for packing and unpacking the binding and type fields:
1183 .Bl -tag -width "ELF32_ST_INFO(bind, type)" -compact
1185 .Fn ELF32_ST_BIND info
1188 .Fn ELF64_ST_BIND info
1189 extract a binding from an st_info value.
1191 .Fn ELF64_ST_TYPE info
1194 .Fn ELF32_ST_TYPE info
1195 extract a type from an st_info value.
1197 .Fn ELF32_ST_INFO bind type
1200 .Fn ELF64_ST_INFO bind type
1201 convert a binding and a type into an st_info value.
1206 This member currently holds zero and has no defined meaning.
1208 Every symbol table entry is
1210 in relation to some section.
1211 This member holds the relevant section
1215 Relocation is the process of connecting symbolic references with
1216 symbolic definitions.
1217 Relocatable files must have information that
1218 describes how to modify their section contents, thus allowing executable
1219 and shared object files to hold the right information for a process'
1221 Relocation entries are these data.
1223 Relocation structures that do not need an addend:
1224 .Bd -literal -offset indent
1226 Elf32_Addr r_offset;
1230 .Bd -literal -offset indent
1232 Elf64_Addr r_offset;
1237 Relocation structures that need an addend:
1238 .Bd -literal -offset indent
1240 Elf32_Addr r_offset;
1242 Elf32_Sword r_addend;
1245 .Bd -literal -offset indent
1247 Elf64_Addr r_offset;
1249 Elf64_Sxword r_addend;
1253 .Bl -tag -width "r_offset" -compact
1255 This member gives the location at which to apply the relocation action.
1256 For a relocatable file, the value is the byte offset from the beginning
1257 of the section to the storage unit affected by the relocation.
1259 executable file or shared object, the value is the virtual address of
1260 the storage unit affected by the relocation.
1262 This member gives both the symbol table index with respect to which the
1263 relocation must be made and the type of relocation to apply.
1265 types are processor-specific.
1266 When the text refers to a relocation
1267 entry's relocation type or symbol table index, it means the result of
1269 .Sy ELF_[32|64]_R_TYPE
1271 .Sy ELF[32|64]_R_SYM ,
1272 respectively to the entry's
1276 This member specifies a constant addend used to compute the value to be
1277 stored into the relocatable field.
1289 .%B Elf-64 Object File Format
1292 .%A Santa Cruz Operation
1293 .%B System V Application Binary Interface
1296 .%A Unix System Laboratories
1298 .%B "Executable and Linking Format (ELF)"
1301 The ELF header files made their appearance in
1303 ELF in itself first appeared in
1305 The ELF format is an adopted standard.
1307 This manual page was written by
1308 .An Jeroen Ruigrok van der Werven
1309 .Aq asmodai@FreeBSD.org
1310 with inspiration from BSDi's