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
25 .\" $FreeBSD: src/share/man/man5/elf.5,v 1.6.2.8 2001/12/17 11:30:13 ru Exp $
26 .\" $DragonFly: src/share/man/man5/elf.5,v 1.4 2006/05/26 19:39:40 swildner Exp $
33 .Nd format of ELF executable binary files
39 defines the format of ELF executable binary files.
40 Amongst these files are
41 normal executable files, relocatable object files, core files and shared
44 An executable file using the ELF file format consists of an ELF header,
45 followed by a program header table or a section header table, or both.
46 The ELF header is always at offset zero of the file.
48 table and the section header table's offset in the file are defined in the
50 The two tables describe the rest of the particularities of
53 Applications which wish to process ELF binary files for their native
54 architecture only should include
57 These applications should need to refer to
58 all the types and structures by their generic names
62 Applications written this way can be compiled on any architecture,
63 regardless whether the host is 32-bit or 64-bit.
65 Should an application need to process ELF files of an unknown
66 architecture then the application needs to include both
72 Furthermore, all types and structures need to be identified by either
76 The macros need to be identified by
81 Whatever the system's architecture is, it will always include
84 .In sys/elf_generic.h .
86 These header files describe the above mentioned headers as C structures
87 and also include structures for dynamic sections, relocation sections and
90 The following types are being used for 32-bit architectures:
91 .Bd -literal -offset indent
92 Elf32_Addr Unsigned program address
93 Elf32_Half Unsigned halfword field
94 Elf32_Off Unsigned file offset
95 Elf32_Sword Signed large integer
96 Elf32_Word Field or unsigned large integer
97 Elf32_Size Unsigned object size
100 For 64-bit architectures we have the following types:
101 .Bd -literal -offset indent
102 Elf64_Addr Unsigned program address
103 Elf64_Half Unsigned halfword field
104 Elf64_Off Unsigned file offset
105 Elf64_Sword Signed large integer
106 Elf64_Word Field or unsigned large integer
107 Elf64_Size Unsigned object size
108 Elf64_Quarter Unsigned quarterword field
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;
138 .Bd -literal -offset indent
140 unsigned char e_ident[EI_NIDENT];
141 Elf64_Quarter e_type;
142 Elf64_Quarter e_machine;
143 Elf64_Half e_version;
148 Elf64_Quarter e_ehsize;
149 Elf64_Quarter e_phentsize;
150 Elf64_Quarter e_phnum;
151 Elf64_Quarter e_shentsize;
152 Elf64_Quarter e_shnum;
153 Elf64_Quarter e_shstrndx;
157 The fields have the following meanings:
159 .Bl -tag -width "e_phentsize" -compact -offset indent
161 This array of bytes specifies to interpret the file,
162 independent of the processor or the file's remaining contents.
163 Within this array everything is named by macros, which start with
166 and may contain values which start with the prefix
168 The following macros are defined:
170 .Bl -tag -width "EI_ABIVERSION" -compact
172 The first byte of the magic number.
173 It must be filled with
176 The second byte of the magic number.
177 It must be filled with
180 The third byte of the magic number.
181 It must be filled with
184 The fourth byte of the magic number.
185 It must be filled with
188 The fifth byte identifies the architecture for this binary:
190 .Bl -tag -width "ELFCLASSNONE" -compact
192 This class is invalid.
194 This defines the 32-bit architecture.
195 It supports machines with files
196 and virtual address spaces up to 4 Gigabytes.
198 This defines the 64-bit architecture.
201 The sixth byte specifies the data encoding of the processor-specific
203 Currently these encodings are supported:
205 .Bl -tag -width "ELFDATA2LSB" -compact
209 Two's complement, little-endian.
211 Two's complement, big-endian.
214 The version number of the ELF specification:
216 .Bl -tag -width "EV_CURRENT" -compact
223 This byte identifies the operating system
224 and ABI to which the object is targeted.
225 Some fields in other ELF structures have flags
226 and values that have platform specific meanings;
227 the interpretation of those fields is determined by the value of this byte.
228 The following values are currently defined:
230 .Bl -tag -width "ELFOSABI_STANDALONE" -compact
234 HP-UX operating system ABI.
235 .It Dv ELFOSABI_NETBSD
237 operating system ABI.
238 .It Dv ELFOSABI_LINUX
239 GNU/Linux operating system ABI.
241 GNU/Hurd operating system ABI.
242 .It Dv ELFOSABI_86OPEN
243 86Open Common IA32 ABI.
244 .It Dv ELFOSABI_SOLARIS
245 Solaris operating system ABI.
246 .It Dv ELFOSABI_MONTEREY
247 Monterey project ABI.
249 IRIX operating system ABI.
250 .It Dv ELFOSABI_FREEBSD
252 operating system ABI.
253 .It Dv ELFOSABI_TRU64
254 TRU64 UNIX operating system ABI.
256 ARM architecture ABI.
257 .It Dv ELFOSABI_STANDALONE
258 Standalone (embedded) ABI.
261 This byte identifies the version of the ABI
262 to which the object is targeted.
263 This field is used to distinguish among incompatible versions of an ABI.
264 The interpretation of this version number
265 is dependent on the ABI identified by the EI_OSABI field.
266 Applications conforming to this specification use the value 0.
269 These bytes are reserved and set to zero.
271 which read them should ignore them.
272 The value for EI_PAD will change in
273 the future if currently unused bytes are given meanings.
275 Start of architecture identification.
277 The size of the e_ident array.
281 This member of the structure identifies the object file type:
283 .Bl -tag -width "ET_NONE" -compact
297 This member specifies the required architecture for an individual file:
299 .Bl -tag -width "EM_MIPS_RS4_BE" -compact
305 Sun Microsystems SPARC.
315 MIPS RS3000 (big-endian only).
316 .It Dv EM_MIPS_RS4_BE
317 MIPS RS4000 (big-endian only).
319 SPARC v9 64-bit unofficial.
329 This member identifies the file version:
331 .Bl -tag -width "EV_CURRENT" -compact
338 This member gives the virtual address to which the system first transfers
339 control, thus starting the process.
340 If the file has no associated entry
341 point, this member holds zero.
343 This member holds the program header table's file offset in bytes.
345 the file has no program header table, this member holds zero.
347 This member holds the section header table's file offset in bytes.
349 file has no section header table this member holds zero.
351 This member holds processor-specific flags associated with the file.
353 names take the form EF_`machine_flag'. Currently no flags have been defined.
355 This member holds the ELF header's size in bytes.
357 This member holds the size in bytes of one entry in the file's program header
358 table; all entries are the same size.
360 This member holds the number of entries in the program header
366 gives the table's size
368 If a file has no program header,
370 holds the value zero.
372 This member holds a sections header's size in bytes.
373 A section header is one
374 entry in the section header table; all entries are the same size.
376 This member holds the number of entries in the section header table.
382 gives the section header table's size in bytes.
383 If a file has no section
386 holds the value of zero.
388 This member holds the section header table index of the entry associated
389 with the section name string table.
390 If the file has no section name string
391 table, this member holds the value
394 .Bl -tag -width "SHN_LORESERVE" -compact
396 This value marks an undefined, missing, irrelevant, or otherwise meaningless
398 For example, a symbol
400 relative to section number
402 is an undefined symbol.
404 This value specifies the lower bound of the range of reserved indexes.
406 This value up to and including
408 are reserved for processor-specific semantics.
410 This value down to and including
412 are reserved for processor-specific semantics.
414 This value specifies absolute values for the corresponding reference.
416 example, symbols defined relative to section number
418 have absolute values and are not affected by relocation.
420 Symbols defined relative to this section are common symbols, such as Fortran
421 COMMON or unallocated C external variables.
423 This value specifies the upper bound of the range of the range of reserved
428 inclusive; the values do
429 not reference the section header table.
430 That is, the section header table
433 contain entries for the reserved indices.
437 An executable or shared object file's program header table is an array of
438 structures, each describing a segment or other information the system needs
439 to prepare the program for execution.
444 Program headers are meaningful only for executable and shared object files.
445 A file specifies its own program header size with the ELF header's
450 As with the Elf executable header, the program header
451 also has different versions depending on the architecture:
453 .Bd -literal -offset indent
466 .Bd -literal -offset indent
479 The main difference between the 32-bit and the 64-bit program header lies
480 only in the location of a
482 member in the total struct.
484 .Bl -tag -width "p_offset" -compact -offset indent
486 This member of the Phdr struct tells what kind of segment this array
487 element describes or how to interpret the array element's information.
488 .Bl -tag -width "PT_DYNAMIC" -compact
491 The array element is unused and the other members' values are undefined.
492 This lets the program header have ignored entries.
494 The array element specifies a loadable segment, described by
498 The bytes from the file are mapped to the beginning of the memory
500 If the segment's memory size
502 is larger than the file size
506 bytes are defined to hold the value 0 and to follow the segment's
508 The file size may not be larger than the memory size.
509 Loadable segment entries in the program header table appear in ascending
514 The array element specifies dynamic linking information.
516 The array element specifies the location and size of a null-terminated
517 path name to invoke as an interpreter.
518 This segment type is meaningful
519 only for executable files (though it may occur for shared objects). However
520 it may not occur more than once in a file.
521 If it is present it must precede
522 any loadable segment entry.
524 The array element specifies the location and size for auxiliary information.
526 This segment type is reserved but has unspecified semantics.
528 contain an array element of this type do not conform to the ABI.
530 The array element, if present, specifies the location and size of the program
531 header table itself, both in the file and in the memory image of the program.
532 This segment type may not occur more than once in a file.
534 only occur if the program header table is part of the memory image of the
536 If it is present it must precede any loadable segment entry.
538 This value up to and including
540 are reserved for processor-specific semantics.
542 This value down to and including
544 are reserved for processor-specific semantics.
548 This member holds the offset from the beginning of the file at which
549 the first byte of the of the segment resides.
551 This member holds the virtual address at which the first byte of the
552 segment resides in memory.
554 On systems for which physical addressing is relevant, this member is
555 reserved for the segment's physical address.
559 not used and must be zero.
561 This member holds the number of bytes in the file image of the segment.
564 This member holds the number of bytes in the memory image of the segment.
567 This member holds flags relevant to the segment:
569 .Bl -tag -width "PF_X" -compact
571 An executable segment.
578 A text segment commonly has the flags
582 A data segment commonly has
588 This member holds the value to which the segments are aligned in memory
590 Loadable process segments must have congruent values for
594 modulo the page size.
595 Values of zero and one mean no alignment is required.
598 should be a positive, integral power of two, and
606 An file's section header table lets one locate all the file's sections.
608 section header table is an array of Elf32_Shdr or Elf64_Shdr structures.
612 member gives the byte offset from the beginning of the file to the section
615 holds the number of entries the section header table contains.
617 holds the size in bytes of each entry.
619 A section header table index is a subscript into this array.
621 header table indices are reserved.
622 An object file does not have sections for
623 these special indices:
625 .Bl -tag -width "SHN_LORESERVE" -compact
627 This value marks an undefined, missing, irrelevant or otherwise meaningless
630 This value specifies the lower bound of the range of reserved indices.
632 This value up to and including
634 are reserved for processor-specific semantics.
636 This value down to and including
638 are reserved for processor-specific semantics.
640 This value specifies absolute values for the corresponding reference.
642 example, symbols defined relative to section number
644 have absolute values and are not affected by relocation.
646 Symbols defined relative to this section are common symbols, such as FORTRAN
647 COMMON or unallocated C external variables.
649 This value specifies the upper bound of the range of reserved indices.
651 system reserves indices between
656 The section header table does not contain entries for the
660 The section header has the following structure:
661 .Bd -literal -offset indent
671 Elf32_Size sh_addralign;
672 Elf32_Size sh_entsize;
676 .Bd -literal -offset indent
686 Elf64_Size sh_addralign;
687 Elf64_Size sh_entsize;
691 .Bl -tag -width "sh_addralign" -compact
693 This member specifies the name of the section.
694 Its value is an index
695 into the section header string table section, giving the location of
696 a null-terminated string.
698 This member categorizes the section's contents and semantics.
700 .Bl -tag -width "SHT_PROGBITS" -compact
702 This value marks the section header as inactive.
704 have an associated section.
705 Other members of the section header
706 have undefined values.
708 The section holds information defined by the program, whose
709 format and meaning are determined solely by the program.
711 This section holds a symbol table.
714 provides symbols for link editing, though it may also be used
716 As a complete symbol table, it may contain
717 many symbols unnecessary for dynamic linking.
723 This section holds a string table.
724 An object file may have multiple
725 string table sections.
727 This section holds relocation entries with explicit addends, such
730 for the 32-bit class of object files.
731 An object may have multiple
734 This section holds a symbol hash table.
735 All object participating in
736 dynamic linking must contain a symbol hash table.
738 have only one hash table.
740 This section holds information for dynamic linking.
742 have only one dynamic section.
744 This section holds information that marks the file in some way.
746 A section of this type occupies no space in the file but otherwise
749 Although this section contains no bytes, the
751 member contains the conceptual file offset.
753 This section holds relocation offsets without explicit addends, such
756 for the 32-bit class of object files.
757 An object file may have multiple
760 This section is reserved but has unspecified semantics.
762 This section holds a minimal set of dynamic linking symbols.
764 object file can also contain a
768 This value up to and including
770 are reserved for processor-specific semantics.
772 This value down to and including
774 are reserved for processor-specific semantics.
776 This value specifies the lower bound of the range of indices reserved for
777 application programs.
779 This value specifies the upper bound of the range of indices reserved for
780 application programs.
781 Section types between
785 may be used by the application, without conflicting with current or future
786 system-defined section types.
790 Sections support one-bit flags that describe miscellaneous attributes.
791 If a flag bit is set in
796 Otherwise, the attribute is
799 Undefined attributes are set to zero.
801 .Bl -tag -width "SHF_EXECINSTR" -compact
803 This section contains data that should be writable during process
806 The section occupies memory during process execution.
808 sections do not reside in the memory image of an object file.
810 attribute is off for those sections.
812 The section contains executable machine instructions.
814 All bits included in this mask are reserved for processor-specific
819 If the section will appear in the memory image of a process, this member
820 holds the address at which the section's first byte should reside.
821 Otherwise, the member contains zero.
823 This member's value holds the byte offset from the beginning of the file
824 to the first byte in the section.
827 occupies no space in the file, and its
829 member locates the conceptual placement in the file.
831 This member holds the section's size in bytes.
832 Unless the section type
840 may have a non-zero size, but it occupies no space in the file.
842 This member holds a section header table index link, whose interpretation
843 depends on the section type.
845 This member holds extra information, whose interpretation depends on the
848 Some sections have address alignment constraints.
850 doubleword, the system must ensure doubleword alignment for the entire
852 That is, the value of
854 must be congruent to zero, modulo the value of
856 Only zero and positive integral powers of two are allowed.
858 or one mean the section has no alignment constraints.
860 Some sections hold a table of fixed-sized entries, such as a symbol table.
861 For such a section, this member gives the size in bytes for each entry.
862 This member contains zero if the section does not hold a table of
866 Various sections hold program and control information:
867 .Bl -tag -width ".shstrtab" -compact
869 This section holds uninitialized data that contributes to the program's
871 By definition, the system initializes the data with zeros
872 when the program begins to run.
873 This section is of type
875 The attributes types are
880 This section holds version control information.
881 This section is of type
883 No attribute types are used.
885 This section holds initialized data that contribute to the program's
887 This section is of type
889 The attribute types are
894 This section holds initialized data that contribute to the program's
896 This section is of type
898 The attribute types are
903 This section holds information for symbolic debugging.
906 This section is of type
908 No attribute types are used.
910 This section holds dynamic linking information.
911 The section's attributes
917 bit is set is processor-specific.
918 This section is of type
920 See the attributes above.
922 This section holds strings needed for dynamic linking, most commonly
923 the strings that represent the names associated with symbol table entries.
924 This section is of type
926 The attribute type used is
929 This section holds the dynamic linking symbol table.
930 This section is of type
932 The attribute used is
935 This section holds executable instructions that contribute to the process
937 When a program exits normally the system arranges to
938 execute the code in this section.
939 This section is of type
941 The attributes used are
946 This section holds the global offset table.
947 This section is of type
949 The attributes are processor-specific.
951 This section holds a symbol hash table.
952 This section is of type
954 The attribute used is
957 This section holds executable instructions that contribute to the process
959 When a program starts to run the system arranges to
960 execute the code in this section before calling the main program entry point.
961 This section is of type
963 The attributes used are
968 This section holds the pathname of a program interpreter.
970 a loadable segment that includes the section, the section's attributes will
974 Otherwise, that bit will be off.
975 This section is of type
978 This section holds line number information for symbolic debugging, which
979 describes the correspondence between the program source and the machine code.
980 The contents are unspecified.
981 This section is of type
983 No attribute types are used.
985 This section holds information in the
987 format described below.
988 This section is of type
990 No attribute types are used.
992 This section holds the procedure linkage table.
993 This section is of type
995 The attributes are processor-specific.
997 This section holds relocation information as described below.
999 has a loadable segment that includes relocation, the section's attributes
1003 Otherwise the bit will be off.
1006 is supplied by the section to which the relocations apply.
1010 normally would have the name
1012 This section is of type
1015 This section holds relocation information as described below.
1017 has a loadable segment that includes relocation, the section's attributes
1021 Otherwise the bit will be off.
1024 is supplied by the section to which the relocations apply.
1028 normally would have the name
1030 This section is of type
1033 This section holds read-only data that typically contributes to a
1034 non-writable segment in the process image.
1035 This section is of type
1037 The attribute used is
1040 This section hold read-only data that typically contributes to a
1041 non-writable segment in the process image.
1042 This section is of type
1044 The attribute used is
1047 This section holds section names.
1048 This section is of type
1050 No attribute types are used.
1052 This section holds strings, most commonly the strings that represent the
1053 names associated with symbol table entries.
1054 If the file has a loadable
1055 segment that includes the symbol string table, the section's attributes
1059 Otherwise the bit will be off.
1060 This section is of type
1063 This section holds a symbol table.
1064 If the file has a loadable segment
1065 that includes the symbol table, the section's attributes will include
1069 Otherwise the bit will be off.
1070 This section is of type
1073 This section holds the
1075 or executable instructions, of a program.
1076 This section is of type
1078 The attributes used are
1084 String table sections hold null-terminated character sequences, commonly
1086 The object file uses these strings to represent symbol
1088 One references a string as an index into the string
1090 The first byte, which is index zero, is defined to hold
1092 Similarly, a string table's last byte is defined to
1093 hold a null character, ensuring null termination for all strings.
1095 An object file's symbol table holds information needed to locate and
1096 relocate a program's symbolic definitions and references.
1098 index is a subscript into this array.
1100 .Bd -literal -offset indent
1103 Elf32_Addr st_value;
1105 unsigned char st_info;
1106 unsigned char st_other;
1107 Elf32_Half st_shndx;
1111 .Bd -literal -offset indent
1114 unsigned char st_info;
1115 unsigned char st_other;
1116 Elf64_Quarter st_shndx;
1117 Elf64_Addr st_value;
1122 .Bl -tag -width "st_value" -compact
1124 This member holds an index into the object file's symbol string table,
1125 which holds character representations of the symbol names.
1127 is non-zero, it represents a string table index that gives the symbol
1129 Otherwise, the symbol table has no name.
1131 This member gives the value of the associated symbol.
1133 Many symbols have associated sizes.
1134 This member holds zero if the symbol
1135 has no size or an unknown size.
1137 This member specifies the symbol's type and binding attributes:
1139 .Bl -tag -width "STT_SECTION" -compact
1141 The symbol's type is not defined.
1143 The symbol is associated with a data object.
1145 The symbol is associated with a function or other executable code.
1147 The symbol is associated with a section.
1148 Symbol table entries of
1149 this type exist primarily for relocation and normally have
1153 By convention the symbol's name gives the name of the source file
1154 associated with the object file.
1157 bindings, its section index is
1159 and it precedes the other
1161 symbols of the file, if it is present.
1163 This value up to and including
1165 are reserved for processor-specific semantics.
1167 This value down to and including
1169 are reserved for processor-specific semantics.
1172 .Bl -tag -width "STB_GLOBAL" -compact
1174 Local symbols are not visible outside the object file containing their
1176 Local symbols of the same name may exist in multiple file
1177 without interfering with each other.
1179 Global symbols are visible to all object files being combined.
1181 definition of a global symbol will satisfy another file's undefined
1182 reference to the same symbol.
1184 Weak symbols resemble global symbols, but their definitions have lower
1187 This value up to and including
1189 are reserved for processor-specific semantics.
1191 This value down to and including
1193 are reserved for processor-specific semantics.
1195 There are macros for packing and unpacking the binding and type fields:
1197 .Bl -tag -width "ELF32_ST_INFO(bind, type)" -compact
1199 .Fn ELF32_ST_BIND info
1202 .Fn ELF64_ST_BIND info
1203 extract a binding from an st_info value.
1205 .Fn ELF64_ST_TYPE info
1208 .Fn ELF32_ST_TYPE info
1209 extract a type from an st_info value.
1211 .Fn ELF32_ST_INFO bind type
1214 .Fn ELF64_ST_INFO bind type
1215 convert a binding and a type into an st_info value.
1220 This member currently holds zero and has no defined meaning.
1222 Every symbol table entry is
1224 in relation to some action.
1225 This member holds the relevant section
1229 Relocation is the process of connecting symbolic references with
1230 symbolic definitions.
1231 Relocatable files must have information that
1232 describes how to modify their section contents, thus allowing executable
1233 and shared object files to hold the right information for a process'
1235 Relocation entries are these data.
1237 Relocation structures that do not need an addend:
1239 .Bd -literal -offset indent
1241 Elf32_Addr r_offset;
1245 .Bd -literal -offset indent
1247 Elf64_Addr r_offset;
1252 Relocation structures that need an addend:
1254 .Bd -literal -offset indent
1256 Elf32_Addr r_offset;
1258 Elf32_Sword r_addend;
1261 .Bd -literal -offset indent
1263 Elf64_Addr r_offset;
1269 .Bl -tag -width "r_offset" -compact
1271 This member gives the location at which to apply the relocation action.
1272 For a relocatable file, the value is the byte offset from the beginning
1273 of the section to the storage unit affected by the relocation.
1275 executable file or shared object, the value is the virtual address of
1276 the storage unit affected by the relocation.
1278 This member gives both the symbol table index with respect to which the
1279 relocation must be made and the type of relocation to apply.
1281 types are processor-specific.
1282 When the text refers to a relocation
1283 entry's relocation type or symbol table index, it means the result of
1285 .Sy ELF_[32|64]_R_TYPE
1287 .Sy ELF[32|64]_R_SYM ,
1288 respectively to the entry's
1292 This member specifies a constant addend used to compute the value to be
1293 stored into the relocatable field.
1304 .%B Elf-64 Object File Format
1307 .%A Santa Cruz Operation
1308 .%B System V Application Binary Interface
1311 .%A Unix System Laboratories
1313 .%B "Executable and Linking Format (ELF)"
1316 The ELF header files made their appearance in
1318 ELF in itself first appeared in
1320 The ELF format is an adopted standard.
1322 This manual page was written by
1323 .An Jeroen Ruigrok van der Werven
1324 .Aq asmodai@FreeBSD.org
1325 with inspiration from BSDi's