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.2 2003/06/17 04:37:00 dillon 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 .Pa 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.
317 MIPS RS3000 (big-endian only).
318 .It Dv EM_MIPS_RS4_BE
319 MIPS RS4000 (big-endian only).
321 SPARC v9 64-bit unofficial.
331 This member identifies the file version:
333 .Bl -tag -width "EV_CURRENT" -compact
340 This member gives the virtual address to which the system first transfers
341 control, thus starting the process.
342 If the file has no associated entry
343 point, this member holds zero.
345 This member holds the program header table's file offset in bytes.
347 the file has no program header table, this member holds zero.
349 This member holds the section header table's file offset in bytes.
351 file has no section header table this member holds zero.
353 This member holds processor-specific flags associated with the file.
355 names take the form EF_`machine_flag'. 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
368 gives the table's size
370 If a file has no program header,
372 holds the value zero.
374 This member holds a sections header's size in bytes.
375 A section header is one
376 entry in the section header table; all entries are the same size.
378 This member holds the number of entries in the section header table.
384 gives the section header table's size in bytes.
385 If a file has no section
388 holds the value of zero.
390 This member holds the section header table index of the entry associated
391 with the section name string table.
392 If the file has no section name string
393 table, this member holds the value
396 .Bl -tag -width "SHN_LORESERVE" -compact
398 This value marks an undefined, missing, irrelevant, or otherwise meaningless
400 For example, a symbol
402 relative to section number
404 is an undefined symbol.
406 This value specifies the lower bound of the range of reserved indexes.
408 This value up to and including
410 are reserved for processor-specific semantics.
412 This value down to and including
414 are reserved for processor-specific semantics.
416 This value specifies absolute values for the corresponding reference.
418 example, symbols defined relative to section number
420 have absolute values and are not affected by relocation.
422 Symbols defined relative to this section are common symbols, such as Fortran
423 COMMON or unallocated C external variables.
425 This value specifies the upper bound of the range of the range of reserved
430 inclusive; the values do
431 not reference the section header table.
432 That is, the section header table
435 contain entries for the reserved indices.
439 An executable or shared object file's program header table is an array of
440 structures, each describing a segment or other information the system needs
441 to prepare the program for execution.
446 Program headers are meaningful only for executable and shared object files.
447 A file specifies its own program header size with the ELF header's
452 As with the Elf executable header, the program header
453 also has different versions depending on the architecture:
455 .Bd -literal -offset indent
468 .Bd -literal -offset indent
481 The main difference between the 32-bit and the 64-bit program header lies
482 only in the location of a
484 member in the total struct.
486 .Bl -tag -width "p_offset" -compact -offset indent
488 This member of the Phdr struct tells what kind of segment this array
489 element describes or how to interpret the array element's information.
490 .Bl -tag -width "PT_DYNAMIC" -compact
493 The array element is unused and the other members' values are undefined.
494 This lets the program header have ignored entries.
496 The array element specifies a loadable segment, described by
500 The bytes from the file are mapped to the beginning of the memory
502 If the segment's memory size
504 is larger than the file size
508 bytes are defined to hold the value 0 and to follow the segment's
510 The file size may not be larger than the memory size.
511 Loadable segment entries in the program header table appear in ascending
516 The array element specifies dynamic linking information.
518 The array element specifies the location and size of a null-terminated
519 path name to invoke as an interpreter.
520 This segment type is meaningful
521 only for executable files (though it may occur for shared objects). However
522 it may not occur more than once in a file.
523 If it is present it must precede
524 any loadable segment entry.
526 The array element specifies the location and size for auxiliary information.
528 This segment type is reserved but has unspecified semantics.
530 contain an array element of this type do not conform to the ABI.
532 The array element, if present, specifies the location and size of the program
533 header table itself, both in the file and in the memory image of the program.
534 This segment type may not occur more than once in a file.
536 only occur if the program header table is part of the memory image of the
538 If it is present it must precede any loadable segment entry.
540 This value up to and including
542 are reserved for processor-specific semantics.
544 This value down to and including
546 are reserved for processor-specific semantics.
550 This member holds the offset from the beginning of the file at which
551 the first byte of the of the segment resides.
553 This member holds the virtual address at which the first byte of the
554 segment resides in memory.
556 On systems for which physical addressing is relevant, this member is
557 reserved for the segment's physical address.
561 not used and must be zero.
563 This member holds the number of bytes in the file image of the segment.
566 This member holds the number of bytes in the memory image of the segment.
569 This member holds flags relevant to the segment:
571 .Bl -tag -width "PF_X" -compact
573 An executable segment.
580 A text segment commonly has the flags
584 A data segment commonly has
590 This member holds the value to which the segments are aligned in memory
592 Loadable process segments must have congruent values for
596 modulo the page size.
597 Values of zero and one mean no alignment is required.
600 should be a positive, integral power of two, and
608 An file's section header table lets one locate all the file's sections.
610 section header table is an array of Elf32_Shdr or Elf64_Shdr structures.
614 member gives the byte offset from the beginning of the file to the section
617 holds the number of entries the section header table contains.
619 holds the size in bytes of each entry.
621 A section header table index is a subscript into this array.
623 header table indices are reserved.
624 An object file does not have sections for
625 these special indices:
627 .Bl -tag -width "SHN_LORESERVE" -compact
629 This value marks an undefined, missing, irrelevant or otherwise meaningless
632 This value specifies the lower bound of the range of reserved indices.
634 This value up to and including
636 are reserved for processor-specific semantics.
638 This value down to and including
640 are reserved for processor-specific semantics.
642 This value specifies absolute values for the corresponding reference.
644 example, symbols defined relative to section number
646 have absolute values and are not affected by relocation.
648 Symbols defined relative to this section are common symbols, such as FORTRAN
649 COMMON or unallocated C external variables.
651 This value specifies the upper bound of the range of reserved indices.
653 system reserves indices between
658 The section header table does not contain entries for the
662 The section header has the following structure:
663 .Bd -literal -offset indent
673 Elf32_Size sh_addralign;
674 Elf32_Size sh_entsize;
678 .Bd -literal -offset indent
688 Elf64_Size sh_addralign;
689 Elf64_Size sh_entsize;
693 .Bl -tag -width "sh_addralign" -compact
695 This member specifies the name of the section.
696 Its value is an index
697 into the section header string table section, giving the location of
698 a null-terminated string.
700 This member categorizes the section's contents and semantics.
702 .Bl -tag -width "SHT_PROGBITS" -compact
704 This value marks the section header as inactive.
706 have an associated section.
707 Other members of the section header
708 have undefined values.
710 The section holds information defined by the program, whose
711 format and meaning are determined solely by the program.
713 This section holds a symbol table.
716 provides symbols for link editing, though it may also be used
718 As a complete symbol table, it may contain
719 many symbols unnecessary for dynamic linking.
725 This section holds a string table.
726 An object file may have multiple
727 string table sections.
729 This section holds relocation entries with explicit addends, such
732 for the 32-bit class of object files.
733 An object may have multiple
736 This section holds a symbol hash table.
737 All object participating in
738 dynamic linking must contain a symbol hash table.
740 have only one hash table.
742 This section holds information for dynamic linking.
744 have only one dynamic section.
746 This section holds information that marks the file in some way.
748 A section of this type occupies no space in the file but otherwise
751 Although this section contains no bytes, the
753 member contains the conceptual file offset.
755 This section holds relocation offsets without explicit addends, such
758 for the 32-bit class of object files.
759 An object file may have multiple
762 This section is reserved but has unspecified semantics.
764 This section holds a minimal set of dynamic linking symbols.
766 object file can also contain a
770 This value up to and including
772 are reserved for processor-specific semantics.
774 This value down to and including
776 are reserved for processor-specific semantics.
778 This value specifies the lower bound of the range of indices reserved for
779 application programs.
781 This value specifies the upper bound of the range of indices reserved for
782 application programs.
783 Section types between
787 may be used by the application, without conflicting with current or future
788 system-defined section types.
792 Sections support one-bit flags that describe miscellaneous attributes.
793 If a flag bit is set in
798 Otherwise, the attribute is
801 Undefined attributes are set to zero.
803 .Bl -tag -width "SHF_EXECINSTR" -compact
805 This section contains data that should be writable during process
808 The section occupies memory during process execution.
810 sections do not reside in the memory image of an object file.
812 attribute is off for those sections.
814 The section contains executable machine instructions.
816 All bits included in this mask are reserved for processor-specific
821 If the section will appear in the memory image of a process, this member
822 holds the address at which the section's first byte should reside.
823 Otherwise, the member contains zero.
825 This member's value holds the byte offset from the beginning of the file
826 to the first byte in the section.
829 occupies no space in the file, and its
831 member locates the conceptual placement in the file.
833 This member holds the section's size in bytes.
834 Unless the section type
842 may have a non-zero size, but it occupies no space in the file.
844 This member holds a section header table index link, whose interpretation
845 depends on the section type.
847 This member holds extra information, whose interpretation depends on the
850 Some sections have address alignment constraints.
852 doubleword, the system must ensure doubleword alignment for the entire
854 That is, the value of
856 must be congruent to zero, modulo the value of
858 Only zero and positive integral powers of two are allowed.
860 or one mean the section has no alignment constraints.
862 Some sections hold a table of fixed-sized entries, such as a symbol table.
863 For such a section, this member gives the size in bytes for each entry.
864 This member contains zero if the section does not hold a table of
868 Various sections hold program and control information:
869 .Bl -tag -width ".shstrtab" -compact
871 This section holds uninitialized data that contributes to the program's
873 By definition, the system initializes the data with zeros
874 when the program begins to run.
875 This section is of type
877 The attributes types are
882 This section holds version control information.
883 This section is of type
885 No attribute types are used.
887 This section holds initialized data that contribute to the program's
889 This section is of type
891 The attribute types are
896 This section holds initialized data that contribute to the program's
898 This section is of type
900 The attribute types are
905 This section holds information for symbolic debugging.
908 This section is of type
910 No attribute types are used.
912 This section holds dynamic linking information.
913 The section's attributes
919 bit is set is processor-specific.
920 This section is of type
922 See the attributes above.
924 This section holds strings needed for dynamic linking, most commonly
925 the strings that represent the names associated with symbol table entries.
926 This section is of type
928 The attribute type used is
931 This section holds the dynamic linking symbol table.
932 This section is of type
934 The attribute used is
937 This section holds executable instructions that contribute to the process
939 When a program exits normally the system arranges to
940 execute the code in this section.
941 This section is of type
943 The attributes used are
948 This section holds the global offset table.
949 This section is of type
951 The attributes are processor-specific.
953 This section holds a symbol hash table.
954 This section is of type
956 The attribute used is
959 This section holds executable instructions that contribute to the process
961 When a program starts to run the system arranges to
962 execute the code in this section before calling the main program entry point.
963 This section is of type
965 The attributes used are
970 This section holds the pathname of a program interpreter.
972 a loadable segment that includes the section, the section's attributes will
976 Otherwise, that bit will be off.
977 This section is of type
980 This section holds line number information for symbolic debugging, which
981 describes the correspondence between the program source and the machine code.
982 The contents are unspecified.
983 This section is of type
985 No attribute types are used.
987 This section holds information in the
989 format described below.
990 This section is of type
992 No attribute types are used.
994 This section holds the procedure linkage table.
995 This section is of type
997 The attributes are processor-specific.
999 This section holds relocation information as described below.
1001 has a loadable segment that includes relocation, the section's attributes
1005 Otherwise the bit will be off.
1008 is supplied by the section to which the relocations apply.
1012 normally would have the name
1014 This section is of type
1017 This section holds relocation information as described below.
1019 has a loadable segment that includes relocation, the section's attributes
1023 Otherwise the bit will be off.
1026 is supplied by the section to which the relocations apply.
1030 normally would have the name
1032 This section is of type
1035 This section holds read-only data that typically contributes to a
1036 non-writable segment in the process image.
1037 This section is of type
1039 The attribute used is
1042 This section hold read-only data that typically contributes to a
1043 non-writable segment in the process image.
1044 This section is of type
1046 The attribute used is
1049 This section holds section names.
1050 This section is of type
1052 No attribute types are used.
1054 This section holds strings, most commonly the strings that represent the
1055 names associated with symbol table entries.
1056 If the file has a loadable
1057 segment that includes the symbol string table, the section's attributes
1061 Otherwise the bit will be off.
1062 This section is of type
1065 This section holds a symbol table.
1066 If the file has a loadable segment
1067 that includes the symbol table, the section's attributes will include
1071 Otherwise the bit will be off.
1072 This section is of type
1075 This section holds the
1077 or executable instructions, of a program.
1078 This section is of type
1080 The attributes used are
1086 String table sections hold null-terminated character sequences, commonly
1088 The object file uses these strings to represent symbol
1090 One references a string as an index into the string
1092 The first byte, which is index zero, is defined to hold
1094 Similarly, a string table's last byte is defined to
1095 hold a null character, ensuring null termination for all strings.
1097 An object file's symbol table holds information needed to locate and
1098 relocate a program's symbolic definitions and references.
1100 index is a subscript into this array.
1102 .Bd -literal -offset indent
1105 Elf32_Addr st_value;
1107 unsigned char st_info;
1108 unsigned char st_other;
1109 Elf32_Half st_shndx;
1113 .Bd -literal -offset indent
1116 unsigned char st_info;
1117 unsigned char st_other;
1118 Elf64_Quarter st_shndx;
1119 Elf64_Addr st_value;
1124 .Bl -tag -width "st_value" -compact
1126 This member holds an index into the object file's symbol string table,
1127 which holds character representations of the symbol names.
1129 is non-zero, it represents a string table index that gives the symbol
1131 Otherwise, the symbol table has no name.
1133 This member gives the value of the associated symbol.
1135 Many symbols have associated sizes.
1136 This member holds zero if the symbol
1137 has no size or an unknown size.
1139 This member specifies the symbol's type and binding attributes:
1141 .Bl -tag -width "STT_SECTION" -compact
1143 The symbol's type is not defined.
1145 The symbol is associated with a data object.
1147 The symbol is associated with a function or other executable code.
1149 The symbol is associated with a section.
1150 Symbol table entries of
1151 this type exist primarily for relocation and normally have
1155 By convention the symbol's name gives the name of the source file
1156 associated with the object file.
1159 bindings, its section index is
1161 and it precedes the other
1163 symbols of the file, if it is present.
1165 This value up to and including
1167 are reserved for processor-specific semantics.
1169 This value down to and including
1171 are reserved for processor-specific semantics.
1174 .Bl -tag -width "STB_GLOBAL" -compact
1176 Local symbols are not visible outside the object file containing their
1178 Local symbols of the same name may exist in multiple file
1179 without interfering with each other.
1181 Global symbols are visible to all object files being combined.
1183 definition of a global symbol will satisfy another file's undefined
1184 reference to the same symbol.
1186 Weak symbols resemble global symbols, but their definitions have lower
1189 This value up to and including
1191 are reserved for processor-specific semantics.
1193 This value down to and including
1195 are reserved for processor-specific semantics.
1197 There are macros for packing and unpacking the binding and type fields:
1199 .Bl -tag -width "ELF32_ST_INFO(bind, type)" -compact
1201 .Fn ELF32_ST_BIND info
1204 .Fn ELF64_ST_BIND info
1205 extract a binding from an st_info value.
1207 .Fn ELF64_ST_TYPE info
1210 .Fn ELF32_ST_TYPE info
1211 extract a type from an st_info value.
1213 .Fn ELF32_ST_INFO bind type
1216 .Fn ELF64_ST_INFO bind type
1217 convert a binding and a type into an st_info value.
1222 This member currently holds zero and has no defined meaning.
1224 Every symbol table entry is
1226 in relation to some action.
1227 This member holds the relevant section
1231 Relocation is the process of connecting symbolic references with
1232 symbolic definitions.
1233 Relocatable files must have information that
1234 describes how to modify their section contents, thus allowing executable
1235 and shared object files to hold the right information for a process'
1237 Relocation entries are these data.
1239 Relocation structures that do not need an addend:
1241 .Bd -literal -offset indent
1243 Elf32_Addr r_offset;
1247 .Bd -literal -offset indent
1249 Elf64_Addr r_offset;
1254 Relocation structures that need an addend:
1256 .Bd -literal -offset indent
1258 Elf32_Addr r_offset;
1260 Elf32_Sword r_addend;
1263 .Bd -literal -offset indent
1265 Elf64_Addr r_offset;
1271 .Bl -tag -width "r_offset" -compact
1273 This member gives the location at which to apply the relocation action.
1274 For a relocatable file, the value is the byte offset from the beginning
1275 of the section to the storage unit affected by the relocation.
1277 executable file or shared object, the value is the virtual address of
1278 the storage unit affected by the relocation.
1280 This member gives both the symbol table index with respect to which the
1281 relocation must be made and the type of relocation to apply.
1283 types are processor-specific.
1284 When the text refers to a relocation
1285 entry's relocation type or symbol table index, it means the result of
1287 .Sy ELF_[32|64]_R_TYPE
1289 .Sy ELF[32|64]_R_SYM ,
1290 respectively to the entry's
1294 This member specifies a constant addend used to compute the value to be
1295 stored into the relocatable field.
1306 .%B Elf-64 Object File Format
1309 .%A Santa Cruz Operation
1310 .%B System V Application Binary Interface
1313 .%A Unix System Laboratories
1315 .%B "Executable and Linking Format (ELF)"
1318 The ELF header files made their appearance in
1320 ELF in itself first appeared in
1322 The ELF format is an adopted standard.
1324 This manual page was written by
1325 .An Jeroen Ruigrok van der Werven
1326 .Aq asmodai@FreeBSD.org
1327 with inspiration from BSDi's