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.36 2007/09/08 08:12:31 jkoshy Exp $
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_Off Unsigned 32-bit file offset
94 Elf32_Sword Signed 32-bit field or integer
95 Elf32_Word Unsigned 32-bit field or integer
96 Elf32_Size Unsigned object size
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
109 Elf64_Size Unsigned object size
112 All data structures that the file format defines follow the
114 size and alignment guidelines for the relevant class.
116 data structures contain explicit padding to ensure 4-byte alignment
117 for 4-byte objects, to force structure sizes to a multiple of 4, etc.
119 The ELF header is described by the type Elf32_Ehdr or Elf64_Ehdr:
120 .Bd -literal -offset indent
122 unsigned char e_ident[EI_NIDENT];
124 Elf32_Half e_machine;
125 Elf32_Word e_version;
131 Elf32_Half e_phentsize;
133 Elf32_Half e_shentsize;
135 Elf32_Half e_shstrndx;
138 .Bd -literal -offset indent
140 unsigned char e_ident[EI_NIDENT];
142 Elf64_Half e_machine;
143 Elf64_Word e_version;
149 Elf64_Half e_phentsize;
151 Elf64_Half e_shentsize;
153 Elf64_Half e_shstrndx;
157 The fields have the following meanings:
159 .Bl -tag -width ".Fa 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 ".Dv 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 ".Dv 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 ".Dv 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 ".Dv 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 ".Dv 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
271 Applications conforming to this specification use the value 0.
274 These bytes are reserved and set to zero.
276 which read them should ignore them.
277 The value for EI_PAD will change in
278 the future if currently unused bytes are given meanings.
286 This member of the structure identifies the object file type:
288 .Bl -tag -width ".Dv ET_NONE" -compact
302 This member specifies the required architecture for an individual file:
304 .Bl -tag -width ".Dv EM_MIPS_RS4_BE" -compact
310 Sun Microsystems SPARC.
320 MIPS RS3000 (big-endian only).
321 .It Dv EM_MIPS_RS4_BE
322 MIPS RS4000 (big-endian only).
324 SPARC v9 64-bit unofficial.
334 This member identifies the file version:
336 .Bl -tag -width ".Dv EV_CURRENT" -compact
343 This member gives the virtual address to which the system first transfers
344 control, thus starting the process.
345 If the file has no associated entry
346 point, this member holds zero.
348 This member holds the program header table's file offset in bytes.
350 the file has no program header table, this member holds zero.
352 This member holds the section header table's file offset in bytes.
354 file has no section header table this member holds zero.
356 This member holds processor-specific flags associated with the file.
357 Flag names take the form EF_`machine_flag'.
358 Currently no flags have been defined.
360 This member holds the ELF header's size in bytes.
362 This member holds the size in bytes of one entry in the file's program header
363 table; all entries are the same size.
365 This member holds the number of entries in the program header
371 gives the table's size
373 If a file has no program header,
375 holds the value zero.
377 This member holds a sections header's size in bytes.
378 A section header is one
379 entry in the section header table; all entries are the same size.
381 This member holds the number of entries in the section header table.
387 gives the section header table's size in bytes.
388 If a file has no section
391 holds the value of zero.
393 This member holds the section header table index of the entry associated
394 with the section name string table.
395 If the file has no section name string
396 table, this member holds the value
399 .Bl -tag -width ".Dv SHN_LORESERVE" -compact
401 This value marks an undefined, missing, irrelevant, or otherwise meaningless
403 For example, a symbol
405 relative to section number
407 is an undefined symbol.
409 This value specifies the lower bound of the range of reserved indexes.
411 This value up to and including
413 are reserved for processor-specific semantics.
415 This value down to and including
417 are reserved for processor-specific semantics.
419 This value specifies absolute values for the corresponding reference.
421 example, symbols defined relative to section number
423 have absolute values and are not affected by relocation.
425 Symbols defined relative to this section are common symbols, such as Fortran
426 COMMON or unallocated C external variables.
428 This value specifies the upper bound of the range of the range of reserved
433 inclusive; the values do
434 not reference the section header table.
435 That is, the section header table
438 contain entries for the reserved indices.
442 An executable or shared object file's program header table is an array of
443 structures, each describing a segment or other information the system needs
444 to prepare the program for execution.
449 Program headers are meaningful only for executable and shared object files.
450 A file specifies its own program header size with the ELF header's
455 As with the Elf executable header, the program header
456 also has different versions depending on the architecture:
457 .Bd -literal -offset indent
469 .Bd -literal -offset indent
476 Elf64_Xword p_filesz;
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 ".Fa p_offset" -compact -offset indent
491 struct tells what kind of segment this array
492 element describes or how to interpret the array element's information.
494 .Bl -tag -width ".Dv PT_DYNAMIC" -compact
496 The array element is unused and the other members' values are undefined.
497 This lets the program header have ignored entries.
499 The array element specifies a loadable segment, described by
503 The bytes from the file are mapped to the beginning of the memory
505 If the segment's memory size
507 is larger than the file size
511 bytes are defined to hold the value 0 and to follow the segment's
513 The file size may not be larger than the memory size.
514 Loadable segment entries in the program header table appear in ascending
519 The array element specifies dynamic linking information.
521 The array element specifies the location and size of a null-terminated
522 path name to invoke as an interpreter.
523 This segment type is meaningful
524 only for executable files (though it may occur for shared objects).
525 However, it may not occur more than once in a file.
526 If it is present it must precede
527 any loadable segment entry.
529 The array element specifies the location and size for auxiliary information.
531 This segment type is reserved but has unspecified semantics.
533 contain an array element of this type do not conform to the ABI.
535 The array element, if present, specifies the location and size of the program
536 header table itself, both in the file and in the memory image of the program.
537 This segment type may not occur more than once in a file.
539 only occur if the program header table is part of the memory image of the
541 If it is present it must precede any loadable segment entry.
543 This value up to and including
545 are reserved for processor-specific semantics.
547 This value down to and including
549 are reserved for processor-specific semantics.
553 This member holds the offset from the beginning of the file at which
554 the first byte of the segment resides.
556 This member holds the virtual address at which the first byte of the
557 segment resides in memory.
559 On systems for which physical addressing is relevant, this member is
560 reserved for the segment's physical address.
564 not used and must be zero.
566 This member holds the number of bytes in the file image of the segment.
569 This member holds the number of bytes in the memory image of the segment.
572 This member holds flags relevant to the segment:
574 .Bl -tag -width ".Dv PF_X" -compact
576 An executable segment.
583 A text segment commonly has the flags
587 A data segment commonly has
593 This member holds the value to which the segments are aligned in memory
595 Loadable process segments must have congruent values for
599 modulo the page size.
600 Values of zero and one mean no alignment is required.
603 should be a positive, integral power of two, and
611 An file's section header table lets one locate all the file's sections.
613 section header table is an array of
620 member gives the byte offset from the beginning of the file to the section
623 holds the number of entries the section header table contains.
625 holds the size in bytes of each entry.
627 A section header table index is a subscript into this array.
629 header table indices are reserved.
630 An object file does not have sections for
631 these special indices:
633 .Bl -tag -width ".Dv SHN_LORESERVE" -compact
635 This value marks an undefined, missing, irrelevant, or otherwise meaningless
638 This value specifies the lower bound of the range of reserved indices.
640 This value up to and including
642 are reserved for processor-specific semantics.
644 This value down to and including
646 are reserved for processor-specific semantics.
648 This value specifies absolute values for the corresponding reference.
650 example, symbols defined relative to section number
652 have absolute values and are not affected by relocation.
654 Symbols defined relative to this section are common symbols, such as FORTRAN
655 COMMON or unallocated C external variables.
657 This value specifies the upper bound of the range of reserved indices.
659 system reserves indices between
664 The section header table does not contain entries for the
668 The section header has the following structure:
669 .Bd -literal -offset indent
679 Elf32_Size sh_addralign;
680 Elf32_Size sh_entsize;
683 .Bd -literal -offset indent
687 Elf64_Xword sh_flags;
693 Elf64_Xword sh_addralign;
694 Elf64_Xword sh_entsize;
698 .Bl -tag -width ".Fa sh_addralign" -compact
700 This member specifies the name of the section.
701 Its value is an index
702 into the section header string table section, giving the location of
703 a null-terminated string.
705 This member categorizes the section's contents and semantics.
707 .Bl -tag -width ".Dv SHT_PROGBITS" -compact
709 This value marks the section header as inactive.
711 have an associated section.
712 Other members of the section header
713 have undefined values.
715 The section holds information defined by the program, whose
716 format and meaning are determined solely by the program.
718 This section holds a symbol table.
721 provides symbols for link editing, though it may also be used
723 As a complete symbol table, it may contain
724 many symbols unnecessary for dynamic linking.
730 This section holds a string table.
731 An object file may have multiple
732 string table sections.
734 This section holds relocation entries with explicit addends, such
737 for the 32-bit class of object files.
738 An object may have multiple
741 This section holds a symbol hash table.
742 All object participating in
743 dynamic linking must contain a symbol hash table.
745 have only one hash table.
747 This section holds information for dynamic linking.
749 have only one dynamic section.
751 This section holds information that marks the file in some way.
753 A section of this type occupies no space in the file but otherwise
756 Although this section contains no bytes, the
758 member contains the conceptual file offset.
760 This section holds relocation offsets without explicit addends, such
763 for the 32-bit class of object files.
764 An object file may have multiple
767 This section is reserved but has unspecified semantics.
769 This section holds a minimal set of dynamic linking symbols.
771 object file can also contain a
775 This value up to and including
777 are reserved for processor-specific semantics.
779 This value down to and including
781 are reserved for processor-specific semantics.
783 This value specifies the lower bound of the range of indices reserved for
784 application programs.
786 This value specifies the upper bound of the range of indices reserved for
787 application programs.
788 Section types between
792 may be used by the application, without conflicting with current or future
793 system-defined section types.
797 Sections support one-bit flags that describe miscellaneous attributes.
798 If a flag bit is set in
803 Otherwise, the attribute is
806 Undefined attributes are set to zero.
808 .Bl -tag -width ".Dv SHF_EXECINSTR" -compact
810 This section contains data that should be writable during process
813 The section occupies memory during process execution.
815 sections do not reside in the memory image of an object file.
817 attribute is off for those sections.
819 The section contains executable machine instructions.
821 All bits included in this mask are reserved for processor-specific
826 If the section will appear in the memory image of a process, this member
827 holds the address at which the section's first byte should reside.
828 Otherwise, the member contains zero.
830 This member's value holds the byte offset from the beginning of the file
831 to the first byte in the section.
834 occupies no space in the file, and its
836 member locates the conceptual placement in the file.
838 This member holds the section's size in bytes.
839 Unless the section type
847 may have a non-zero size, but it occupies no space in the file.
849 This member holds a section header table index link, whose interpretation
850 depends on the section type.
852 This member holds extra information, whose interpretation depends on the
855 Some sections have address alignment constraints.
857 doubleword, the system must ensure doubleword alignment for the entire
859 That is, the value of
861 must be congruent to zero, modulo the value of
863 Only zero and positive integral powers of two are allowed.
865 or one mean the section has no alignment constraints.
867 Some sections hold a table of fixed-sized entries, such as a symbol table.
868 For such a section, this member gives the size in bytes for each entry.
869 This member contains zero if the section does not hold a table of
873 Various sections hold program and control information:
874 .Bl -tag -width ".Sy .shstrtab" -compact
876 (Block Started by Symbol)
877 This section holds uninitialized data that contributes to the program's
879 By definition, the system initializes the data with zeros
880 when the program begins to run.
881 This section is of type
883 The attributes types are
888 This section holds version control information.
889 This section is of type
891 No attribute types are used.
893 This section holds initialized data that contribute to the program's
895 This section is of type
897 The attribute types are
902 This section holds initialized data that contribute to the program's
904 This section is of type
906 The attribute types are
911 This section holds information for symbolic debugging.
914 This section is of type
916 No attribute types are used.
918 This section holds dynamic linking information.
919 The section's attributes
925 bit is set is processor-specific.
926 This section is of type
928 See the attributes above.
930 This section holds strings needed for dynamic linking, most commonly
931 the strings that represent the names associated with symbol table entries.
932 This section is of type
934 The attribute type used is
937 This section holds the dynamic linking symbol table.
938 This section is of type
940 The attribute used is
943 This section holds executable instructions that contribute to the process
945 When a program exits normally the system arranges to
946 execute the code in this section.
947 This section is of type
949 The attributes used are
954 This section holds the global offset table.
955 This section is of type
957 The attributes are processor-specific.
959 This section holds a symbol hash table.
960 This section is of type
962 The attribute used is
965 This section holds executable instructions that contribute to the process
967 When a program starts to run the system arranges to
968 execute the code in this section before calling the main program entry point.
969 This section is of type
971 The attributes used are
976 This section holds the pathname of a program interpreter.
978 a loadable segment that includes the section, the section's attributes will
982 Otherwise, that bit will be off.
983 This section is of type
986 This section holds line number information for symbolic debugging, which
987 describes the correspondence between the program source and the machine code.
988 The contents are unspecified.
989 This section is of type
991 No attribute types are used.
993 This section holds information in the
995 format described below.
996 This section is of type
998 No attribute types are used.
1000 This section holds the procedure linkage table.
1001 This section is of type
1003 The attributes are processor-specific.
1005 This section holds relocation information as described below.
1007 has a loadable segment that includes relocation, the section's attributes
1011 Otherwise the bit will be off.
1014 is supplied by the section to which the relocations apply.
1018 normally would have the name
1020 This section is of type
1023 This section holds relocation information as described below.
1025 has a loadable segment that includes relocation, the section's attributes
1029 Otherwise the bit will be off.
1032 is supplied by the section to which the relocations apply.
1036 normally would have the name
1038 This section is of type
1041 This section holds read-only data that typically contributes to a
1042 non-writable segment in the process image.
1043 This section is of type
1045 The attribute used is
1048 This section hold read-only data that typically contributes to a
1049 non-writable segment in the process image.
1050 This section is of type
1052 The attribute used is
1055 This section holds section names.
1056 This section is of type
1058 No attribute types are used.
1060 This section holds strings, most commonly the strings that represent the
1061 names associated with symbol table entries.
1062 If the file has a loadable
1063 segment that includes the symbol string table, the section's attributes
1067 Otherwise the bit will be off.
1068 This section is of type
1071 This section holds a symbol table.
1072 If the file has a loadable segment
1073 that includes the symbol table, the section's attributes will include
1077 Otherwise the bit will be off.
1078 This section is of type
1081 This section holds the
1083 or executable instructions, of a program.
1084 This section is of type
1086 The attributes used are
1092 String table sections hold null-terminated character sequences, commonly
1094 The object file uses these strings to represent symbol
1096 One references a string as an index into the string
1098 The first byte, which is index zero, is defined to hold
1100 Similarly, a string table's last byte is defined to
1101 hold a null character, ensuring null termination for all strings.
1103 An object file's symbol table holds information needed to locate and
1104 relocate a program's symbolic definitions and references.
1106 index is a subscript into this array.
1107 .Bd -literal -offset indent
1110 Elf32_Addr st_value;
1112 unsigned char st_info;
1113 unsigned char st_other;
1114 Elf32_Half st_shndx;
1117 .Bd -literal -offset indent
1120 unsigned char st_info;
1121 unsigned char st_other;
1122 Elf64_Half st_shndx;
1123 Elf64_Addr st_value;
1124 Elf64_Xword st_size;
1128 .Bl -tag -width ".Fa st_value" -compact
1130 This member holds an index into the object file's symbol string table,
1131 which holds character representations of the symbol names.
1133 is non-zero, it represents a string table index that gives the symbol
1135 Otherwise, the symbol table has no name.
1137 This member gives the value of the associated symbol.
1139 Many symbols have associated sizes.
1140 This member holds zero if the symbol
1141 has no size or an unknown size.
1143 This member specifies the symbol's type and binding attributes:
1145 .Bl -tag -width ".Dv STT_SECTION" -compact
1147 The symbol's type is not defined.
1149 The symbol is associated with a data object.
1151 The symbol is associated with a function or other executable code.
1153 The symbol is associated with a section.
1154 Symbol table entries of
1155 this type exist primarily for relocation and normally have
1159 By convention the symbol's name gives the name of the source file
1160 associated with the object file.
1163 bindings, its section index is
1165 and it precedes the other
1167 symbols of the file, if it is present.
1169 This value up to and including
1171 are reserved for processor-specific semantics.
1173 This value down to and including
1175 are reserved for processor-specific semantics.
1178 .Bl -tag -width ".Dv STB_GLOBAL" -compact
1180 Local symbols are not visible outside the object file containing their
1182 Local symbols of the same name may exist in multiple file
1183 without interfering with each other.
1185 Global symbols are visible to all object files being combined.
1187 definition of a global symbol will satisfy another file's undefined
1188 reference to the same symbol.
1190 Weak symbols resemble global symbols, but their definitions have lower
1193 This value up to and including
1195 are reserved for processor-specific semantics.
1197 This value down to and including
1199 are reserved for processor-specific semantics.
1201 There are macros for packing and unpacking the binding and type fields:
1203 .Bl -tag -width ".Fn ELF32_ST_INFO bind type" -compact
1205 .Fn ELF32_ST_BIND info
1208 .Fn ELF64_ST_BIND info
1209 extract a binding from an
1213 .Fn ELF64_ST_TYPE info
1216 .Fn ELF32_ST_TYPE info
1217 extract a type from an
1221 .Fn ELF32_ST_INFO bind type
1224 .Fn ELF64_ST_INFO bind type
1225 convert a binding and a type into an
1232 This member currently holds zero and has no defined meaning.
1234 Every symbol table entry is
1236 in relation to some section.
1237 This member holds the relevant section
1241 Relocation is the process of connecting symbolic references with
1242 symbolic definitions.
1243 Relocatable files must have information that
1244 describes how to modify their section contents, thus allowing executable
1245 and shared object files to hold the right information for a process'
1247 Relocation entries are these data.
1249 Relocation structures that do not need an addend:
1250 .Bd -literal -offset indent
1252 Elf32_Addr r_offset;
1256 .Bd -literal -offset indent
1258 Elf64_Addr r_offset;
1263 Relocation structures that need an addend:
1264 .Bd -literal -offset indent
1266 Elf32_Addr r_offset;
1268 Elf32_Sword r_addend;
1271 .Bd -literal -offset indent
1273 Elf64_Addr r_offset;
1275 Elf64_Sxword r_addend;
1279 .Bl -tag -width ".Fa r_offset" -compact
1281 This member gives the location at which to apply the relocation action.
1282 For a relocatable file, the value is the byte offset from the beginning
1283 of the section to the storage unit affected by the relocation.
1285 executable file or shared object, the value is the virtual address of
1286 the storage unit affected by the relocation.
1288 This member gives both the symbol table index with respect to which the
1289 relocation must be made and the type of relocation to apply.
1291 types are processor-specific.
1292 When the text refers to a relocation
1293 entry's relocation type or symbol table index, it means the result of
1295 .Fn ELF[32|64]_R_TYPE
1297 .Fn ELF[32|64]_R_SYM ,
1298 respectively to the entry's
1302 This member specifies a constant addend used to compute the value to be
1303 stored into the relocatable field.
1315 .%B Elf-64 Object File Format
1318 .%A Santa Cruz Operation
1319 .%B System V Application Binary Interface
1322 .%A Unix System Laboratories
1324 .%B "Executable and Linking Format (ELF)"
1327 The ELF header files made their appearance in
1329 ELF in itself first appeared in
1331 The ELF format is an adopted standard.
1333 This manual page was written by
1334 .An Jeroen Ruigrok van der Werven Aq Mt asmodai@FreeBSD.org
1335 with inspiration from BSDi's