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.5 2007/07/30 22:11:33 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
235 HP-UX operating system ABI.
236 .It Dv ELFOSABI_NETBSD
238 operating system ABI.
239 .It Dv ELFOSABI_LINUX
240 GNU/Linux operating system ABI.
242 GNU/Hurd operating system ABI.
243 .It Dv ELFOSABI_86OPEN
244 86Open Common IA32 ABI.
245 .It Dv ELFOSABI_SOLARIS
246 Solaris operating system ABI.
247 .It Dv ELFOSABI_MONTEREY
248 Monterey project ABI.
250 IRIX operating system ABI.
251 .It Dv ELFOSABI_FREEBSD
253 operating system ABI.
254 .It Dv ELFOSABI_TRU64
257 operating system ABI.
259 ARM architecture ABI.
260 .It Dv ELFOSABI_STANDALONE
261 Standalone (embedded) ABI.
264 This byte identifies the version of the ABI
265 to which the object is targeted.
266 This field is used to distinguish among incompatible versions of an ABI.
267 The interpretation of this version number
268 is dependent on the ABI identified by the EI_OSABI field.
269 Applications conforming to this specification use the value 0.
272 These bytes are reserved and set to zero.
274 which read them should ignore them.
275 The value for EI_PAD will change in
276 the future if currently unused bytes are given meanings.
278 Start of architecture identification.
280 The size of the e_ident array.
284 This member of the structure identifies the object file type:
286 .Bl -tag -width "ET_NONE" -compact
300 This member specifies the required architecture for an individual file:
302 .Bl -tag -width "EM_MIPS_RS4_BE" -compact
308 Sun Microsystems SPARC.
318 MIPS RS3000 (big-endian only).
319 .It Dv EM_MIPS_RS4_BE
320 MIPS RS4000 (big-endian only).
322 SPARC v9 64-bit unofficial.
332 This member identifies the file version:
334 .Bl -tag -width "EV_CURRENT" -compact
341 This member gives the virtual address to which the system first transfers
342 control, thus starting the process.
343 If the file has no associated entry
344 point, this member holds zero.
346 This member holds the program header table's file offset in bytes.
348 the file has no program header table, this member holds zero.
350 This member holds the section header table's file offset in bytes.
352 file has no section header table this member holds zero.
354 This member holds processor-specific flags associated with the file.
356 names take the form EF_`machine_flag'. Currently no flags have been defined.
358 This member holds the ELF header's size in bytes.
360 This member holds the size in bytes of one entry in the file's program header
361 table; all entries are the same size.
363 This member holds the number of entries in the program header
369 gives the table's size
371 If a file has no program header,
373 holds the value zero.
375 This member holds a sections header's size in bytes.
376 A section header is one
377 entry in the section header table; all entries are the same size.
379 This member holds the number of entries in the section header table.
385 gives the section header table's size in bytes.
386 If a file has no section
389 holds the value of zero.
391 This member holds the section header table index of the entry associated
392 with the section name string table.
393 If the file has no section name string
394 table, this member holds the value
397 .Bl -tag -width "SHN_LORESERVE" -compact
399 This value marks an undefined, missing, irrelevant, or otherwise meaningless
401 For example, a symbol
403 relative to section number
405 is an undefined symbol.
407 This value specifies the lower bound of the range of reserved indexes.
409 This value up to and including
411 are reserved for processor-specific semantics.
413 This value down to and including
415 are reserved for processor-specific semantics.
417 This value specifies absolute values for the corresponding reference.
419 example, symbols defined relative to section number
421 have absolute values and are not affected by relocation.
423 Symbols defined relative to this section are common symbols, such as Fortran
424 COMMON or unallocated C external variables.
426 This value specifies the upper bound of the range of the range of reserved
431 inclusive; the values do
432 not reference the section header table.
433 That is, the section header table
436 contain entries for the reserved indices.
440 An executable or shared object file's program header table is an array of
441 structures, each describing a segment or other information the system needs
442 to prepare the program for execution.
447 Program headers are meaningful only for executable and shared object files.
448 A file specifies its own program header size with the ELF header's
453 As with the Elf executable header, the program header
454 also has different versions depending on the architecture:
456 .Bd -literal -offset indent
469 .Bd -literal -offset indent
482 The main difference between the 32-bit and the 64-bit program header lies
483 only in the location of a
485 member in the total struct.
487 .Bl -tag -width "p_offset" -compact -offset indent
489 This member of the Phdr struct tells what kind of segment this array
490 element describes or how to interpret the array element's information.
491 .Bl -tag -width "PT_DYNAMIC" -compact
494 The array element is unused and the other members' values are undefined.
495 This lets the program header have ignored entries.
497 The array element specifies a loadable segment, described by
501 The bytes from the file are mapped to the beginning of the memory
503 If the segment's memory size
505 is larger than the file size
509 bytes are defined to hold the value 0 and to follow the segment's
511 The file size may not be larger than the memory size.
512 Loadable segment entries in the program header table appear in ascending
517 The array element specifies dynamic linking information.
519 The array element specifies the location and size of a null-terminated
520 path name to invoke as an interpreter.
521 This segment type is meaningful
522 only for executable files (though it may occur for shared objects). However
523 it may not occur more than once in a file.
524 If it is present it must precede
525 any loadable segment entry.
527 The array element specifies the location and size for auxiliary information.
529 This segment type is reserved but has unspecified semantics.
531 contain an array element of this type do not conform to the ABI.
533 The array element, if present, specifies the location and size of the program
534 header table itself, both in the file and in the memory image of the program.
535 This segment type may not occur more than once in a file.
537 only occur if the program header table is part of the memory image of the
539 If it is present it must precede any loadable segment entry.
541 This value up to and including
543 are reserved for processor-specific semantics.
545 This value down to and including
547 are reserved for processor-specific semantics.
551 This member holds the offset from the beginning of the file at which
552 the first byte of the of the segment resides.
554 This member holds the virtual address at which the first byte of the
555 segment resides in memory.
557 On systems for which physical addressing is relevant, this member is
558 reserved for the segment's physical address.
562 not used and must be zero.
564 This member holds the number of bytes in the file image of the segment.
567 This member holds the number of bytes in the memory image of the segment.
570 This member holds flags relevant to the segment:
572 .Bl -tag -width "PF_X" -compact
574 An executable segment.
581 A text segment commonly has the flags
585 A data segment commonly has
591 This member holds the value to which the segments are aligned in memory
593 Loadable process segments must have congruent values for
597 modulo the page size.
598 Values of zero and one mean no alignment is required.
601 should be a positive, integral power of two, and
609 An file's section header table lets one locate all the file's sections.
611 section header table is an array of Elf32_Shdr or Elf64_Shdr structures.
615 member gives the byte offset from the beginning of the file to the section
618 holds the number of entries the section header table contains.
620 holds the size in bytes of each entry.
622 A section header table index is a subscript into this array.
624 header table indices are reserved.
625 An object file does not have sections for
626 these special indices:
628 .Bl -tag -width "SHN_LORESERVE" -compact
630 This value marks an undefined, missing, irrelevant or otherwise meaningless
633 This value specifies the lower bound of the range of reserved indices.
635 This value up to and including
637 are reserved for processor-specific semantics.
639 This value down to and including
641 are reserved for processor-specific semantics.
643 This value specifies absolute values for the corresponding reference.
645 example, symbols defined relative to section number
647 have absolute values and are not affected by relocation.
649 Symbols defined relative to this section are common symbols, such as FORTRAN
650 COMMON or unallocated C external variables.
652 This value specifies the upper bound of the range of reserved indices.
654 system reserves indices between
659 The section header table does not contain entries for the
663 The section header has the following structure:
664 .Bd -literal -offset indent
674 Elf32_Size sh_addralign;
675 Elf32_Size sh_entsize;
679 .Bd -literal -offset indent
689 Elf64_Size sh_addralign;
690 Elf64_Size sh_entsize;
694 .Bl -tag -width "sh_addralign" -compact
696 This member specifies the name of the section.
697 Its value is an index
698 into the section header string table section, giving the location of
699 a null-terminated string.
701 This member categorizes the section's contents and semantics.
703 .Bl -tag -width "SHT_PROGBITS" -compact
705 This value marks the section header as inactive.
707 have an associated section.
708 Other members of the section header
709 have undefined values.
711 The section holds information defined by the program, whose
712 format and meaning are determined solely by the program.
714 This section holds a symbol table.
717 provides symbols for link editing, though it may also be used
719 As a complete symbol table, it may contain
720 many symbols unnecessary for dynamic linking.
726 This section holds a string table.
727 An object file may have multiple
728 string table sections.
730 This section holds relocation entries with explicit addends, such
733 for the 32-bit class of object files.
734 An object may have multiple
737 This section holds a symbol hash table.
738 All object participating in
739 dynamic linking must contain a symbol hash table.
741 have only one hash table.
743 This section holds information for dynamic linking.
745 have only one dynamic section.
747 This section holds information that marks the file in some way.
749 A section of this type occupies no space in the file but otherwise
752 Although this section contains no bytes, the
754 member contains the conceptual file offset.
756 This section holds relocation offsets without explicit addends, such
759 for the 32-bit class of object files.
760 An object file may have multiple
763 This section is reserved but has unspecified semantics.
765 This section holds a minimal set of dynamic linking symbols.
767 object file can also contain a
771 This value up to and including
773 are reserved for processor-specific semantics.
775 This value down to and including
777 are reserved for processor-specific semantics.
779 This value specifies the lower bound of the range of indices reserved for
780 application programs.
782 This value specifies the upper bound of the range of indices reserved for
783 application programs.
784 Section types between
788 may be used by the application, without conflicting with current or future
789 system-defined section types.
793 Sections support one-bit flags that describe miscellaneous attributes.
794 If a flag bit is set in
799 Otherwise, the attribute is
802 Undefined attributes are set to zero.
804 .Bl -tag -width "SHF_EXECINSTR" -compact
806 This section contains data that should be writable during process
809 The section occupies memory during process execution.
811 sections do not reside in the memory image of an object file.
813 attribute is off for those sections.
815 The section contains executable machine instructions.
817 All bits included in this mask are reserved for processor-specific
822 If the section will appear in the memory image of a process, this member
823 holds the address at which the section's first byte should reside.
824 Otherwise, the member contains zero.
826 This member's value holds the byte offset from the beginning of the file
827 to the first byte in the section.
830 occupies no space in the file, and its
832 member locates the conceptual placement in the file.
834 This member holds the section's size in bytes.
835 Unless the section type
843 may have a non-zero size, but it occupies no space in the file.
845 This member holds a section header table index link, whose interpretation
846 depends on the section type.
848 This member holds extra information, whose interpretation depends on the
851 Some sections have address alignment constraints.
853 doubleword, the system must ensure doubleword alignment for the entire
855 That is, the value of
857 must be congruent to zero, modulo the value of
859 Only zero and positive integral powers of two are allowed.
861 or one mean the section has no alignment constraints.
863 Some sections hold a table of fixed-sized entries, such as a symbol table.
864 For such a section, this member gives the size in bytes for each entry.
865 This member contains zero if the section does not hold a table of
869 Various sections hold program and control information:
870 .Bl -tag -width ".shstrtab" -compact
872 This section holds uninitialized data that contributes to the program's
874 By definition, the system initializes the data with zeros
875 when the program begins to run.
876 This section is of type
878 The attributes types are
883 This section holds version control information.
884 This section is of type
886 No attribute types are used.
888 This section holds initialized data that contribute to the program's
890 This section is of type
892 The attribute types are
897 This section holds initialized data that contribute to the program's
899 This section is of type
901 The attribute types are
906 This section holds information for symbolic debugging.
909 This section is of type
911 No attribute types are used.
913 This section holds dynamic linking information.
914 The section's attributes
920 bit is set is processor-specific.
921 This section is of type
923 See the attributes above.
925 This section holds strings needed for dynamic linking, most commonly
926 the strings that represent the names associated with symbol table entries.
927 This section is of type
929 The attribute type used is
932 This section holds the dynamic linking symbol table.
933 This section is of type
935 The attribute used is
938 This section holds executable instructions that contribute to the process
940 When a program exits normally the system arranges to
941 execute the code in this section.
942 This section is of type
944 The attributes used are
949 This section holds the global offset table.
950 This section is of type
952 The attributes are processor-specific.
954 This section holds a symbol hash table.
955 This section is of type
957 The attribute used is
960 This section holds executable instructions that contribute to the process
962 When a program starts to run the system arranges to
963 execute the code in this section before calling the main program entry point.
964 This section is of type
966 The attributes used are
971 This section holds the pathname of a program interpreter.
973 a loadable segment that includes the section, the section's attributes will
977 Otherwise, that bit will be off.
978 This section is of type
981 This section holds line number information for symbolic debugging, which
982 describes the correspondence between the program source and the machine code.
983 The contents are unspecified.
984 This section is of type
986 No attribute types are used.
988 This section holds information in the
990 format described below.
991 This section is of type
993 No attribute types are used.
995 This section holds the procedure linkage table.
996 This section is of type
998 The attributes are processor-specific.
1000 This section holds relocation information as described below.
1002 has a loadable segment that includes relocation, the section's attributes
1006 Otherwise the bit will be off.
1009 is supplied by the section to which the relocations apply.
1013 normally would have the name
1015 This section is of type
1018 This section holds relocation information as described below.
1020 has a loadable segment that includes relocation, the section's attributes
1024 Otherwise the bit will be off.
1027 is supplied by the section to which the relocations apply.
1031 normally would have the name
1033 This section is of type
1036 This section holds read-only data that typically contributes to a
1037 non-writable segment in the process image.
1038 This section is of type
1040 The attribute used is
1043 This section hold read-only data that typically contributes to a
1044 non-writable segment in the process image.
1045 This section is of type
1047 The attribute used is
1050 This section holds section names.
1051 This section is of type
1053 No attribute types are used.
1055 This section holds strings, most commonly the strings that represent the
1056 names associated with symbol table entries.
1057 If the file has a loadable
1058 segment that includes the symbol string table, the section's attributes
1062 Otherwise the bit will be off.
1063 This section is of type
1066 This section holds a symbol table.
1067 If the file has a loadable segment
1068 that includes the symbol table, the section's attributes will include
1072 Otherwise the bit will be off.
1073 This section is of type
1076 This section holds the
1078 or executable instructions, of a program.
1079 This section is of type
1081 The attributes used are
1087 String table sections hold null-terminated character sequences, commonly
1089 The object file uses these strings to represent symbol
1091 One references a string as an index into the string
1093 The first byte, which is index zero, is defined to hold
1095 Similarly, a string table's last byte is defined to
1096 hold a null character, ensuring null termination for all strings.
1098 An object file's symbol table holds information needed to locate and
1099 relocate a program's symbolic definitions and references.
1101 index is a subscript into this array.
1103 .Bd -literal -offset indent
1106 Elf32_Addr st_value;
1108 unsigned char st_info;
1109 unsigned char st_other;
1110 Elf32_Half st_shndx;
1114 .Bd -literal -offset indent
1117 unsigned char st_info;
1118 unsigned char st_other;
1119 Elf64_Quarter st_shndx;
1120 Elf64_Addr st_value;
1125 .Bl -tag -width "st_value" -compact
1127 This member holds an index into the object file's symbol string table,
1128 which holds character representations of the symbol names.
1130 is non-zero, it represents a string table index that gives the symbol
1132 Otherwise, the symbol table has no name.
1134 This member gives the value of the associated symbol.
1136 Many symbols have associated sizes.
1137 This member holds zero if the symbol
1138 has no size or an unknown size.
1140 This member specifies the symbol's type and binding attributes:
1142 .Bl -tag -width "STT_SECTION" -compact
1144 The symbol's type is not defined.
1146 The symbol is associated with a data object.
1148 The symbol is associated with a function or other executable code.
1150 The symbol is associated with a section.
1151 Symbol table entries of
1152 this type exist primarily for relocation and normally have
1156 By convention the symbol's name gives the name of the source file
1157 associated with the object file.
1160 bindings, its section index is
1162 and it precedes the other
1164 symbols of the file, if it is present.
1166 This value up to and including
1168 are reserved for processor-specific semantics.
1170 This value down to and including
1172 are reserved for processor-specific semantics.
1175 .Bl -tag -width "STB_GLOBAL" -compact
1177 Local symbols are not visible outside the object file containing their
1179 Local symbols of the same name may exist in multiple file
1180 without interfering with each other.
1182 Global symbols are visible to all object files being combined.
1184 definition of a global symbol will satisfy another file's undefined
1185 reference to the same symbol.
1187 Weak symbols resemble global symbols, but their definitions have lower
1190 This value up to and including
1192 are reserved for processor-specific semantics.
1194 This value down to and including
1196 are reserved for processor-specific semantics.
1198 There are macros for packing and unpacking the binding and type fields:
1200 .Bl -tag -width "ELF32_ST_INFO(bind, type)" -compact
1202 .Fn ELF32_ST_BIND info
1205 .Fn ELF64_ST_BIND info
1206 extract a binding from an st_info value.
1208 .Fn ELF64_ST_TYPE info
1211 .Fn ELF32_ST_TYPE info
1212 extract a type from an st_info value.
1214 .Fn ELF32_ST_INFO bind type
1217 .Fn ELF64_ST_INFO bind type
1218 convert a binding and a type into an st_info value.
1223 This member currently holds zero and has no defined meaning.
1225 Every symbol table entry is
1227 in relation to some action.
1228 This member holds the relevant section
1232 Relocation is the process of connecting symbolic references with
1233 symbolic definitions.
1234 Relocatable files must have information that
1235 describes how to modify their section contents, thus allowing executable
1236 and shared object files to hold the right information for a process'
1238 Relocation entries are these data.
1240 Relocation structures that do not need an addend:
1242 .Bd -literal -offset indent
1244 Elf32_Addr r_offset;
1248 .Bd -literal -offset indent
1250 Elf64_Addr r_offset;
1255 Relocation structures that need an addend:
1257 .Bd -literal -offset indent
1259 Elf32_Addr r_offset;
1261 Elf32_Sword r_addend;
1264 .Bd -literal -offset indent
1266 Elf64_Addr r_offset;
1272 .Bl -tag -width "r_offset" -compact
1274 This member gives the location at which to apply the relocation action.
1275 For a relocatable file, the value is the byte offset from the beginning
1276 of the section to the storage unit affected by the relocation.
1278 executable file or shared object, the value is the virtual address of
1279 the storage unit affected by the relocation.
1281 This member gives both the symbol table index with respect to which the
1282 relocation must be made and the type of relocation to apply.
1284 types are processor-specific.
1285 When the text refers to a relocation
1286 entry's relocation type or symbol table index, it means the result of
1288 .Sy ELF_[32|64]_R_TYPE
1290 .Sy ELF[32|64]_R_SYM ,
1291 respectively to the entry's
1295 This member specifies a constant addend used to compute the value to be
1296 stored into the relocatable field.
1307 .%B Elf-64 Object File Format
1310 .%A Santa Cruz Operation
1311 .%B System V Application Binary Interface
1314 .%A Unix System Laboratories
1316 .%B "Executable and Linking Format (ELF)"
1319 The ELF header files made their appearance in
1321 ELF in itself first appeared in
1323 The ELF format is an adopted standard.
1325 This manual page was written by
1326 .An Jeroen Ruigrok van der Werven
1327 .Aq asmodai@FreeBSD.org
1328 with inspiration from BSDi's