IA: Relocation Types (Linker and Libraries Guide)

Linker and Libraries Guide

IA: Relocation Types

The relocations listed in the following table are defined for 32-bit IA.

Table 7-29 IA: ELF Relocation Types


Name	Value	Field	Calculation
`R_386_NONE`	`0`	none	none
`R_386_32`	`1`	`word32`	`S + A`
`R_386_PC32`	`2`	`word32`	`S + A - P`
`R_386_GOT32`	`3`	`word32`	`G + A`
`R_386_PLT32`	`4`	`word32`	`L + A - P`
`R_386_COPY`	`5`	none	none
`R_386_GLOB_DAT`	`6`	`word32`	`S`
`R_386_JMP_SLOT`	`7`	`word32`	`S`
`R_386_RELATIVE`	`8`	`word32`	`B + A`
`R_386_GOTOFF`	`9`	`word32`	`S + A - GOT`
`R_386_GOTPC`	`10`	`word32`	`GOT + A - P`
`R_386_32PLT`	`11`	`word32`	`L + A`

Some relocation types have semantics beyond simple calculation:

R_386_GOT32: Computes the distance from the base of the global offset table to the symbol's global offset table entry. It also instructs the link-editor to create a global offset table.
R_386_PLT32: Computes the address of the symbol's procedure linkage table entry and instructs the link-editor to create a procedure linkage table.
R_386_COPY: Created by the link-editor for dynamic executables to preserve a read-only text segment. Its offset member refers to a location in a writable segment. The symbol table index specifies a symbol that should exist both in the current object file and in a shared object. During execution, the runtime linker copies data associated with the shared object's symbol to the location specified by the offset. See "Copy Relocations".
R_386_GLOB_DAT: Used to set a global offset table entry to the address of the specified symbol. The special relocation type enable you to determine the correspondence between symbols and global offset table entries.
R_386_JMP_SLOT: Created by the link-editor for dynamic objects to provide lazy binding. Its offset member gives the location of a procedure linkage table entry. The runtime linker modifies the procedure linkage table entry to transfer control to the designated symbol address.
R_386_RELATIVE: Created by the link-editor for dynamic objects. Its offset member gives the location within a shared object that contains a value representing a relative address. The runtime linker computes the corresponding virtual address by adding the virtual address at which the shared object is loaded to the relative address. Relocation entries for this type must specify 0 for the symbol table index.
R_386_GOTOFF: Computes the difference between a symbol's value and the address of the global offset table. It also instructs the link-editor to create the global offset table.
R_386_GOTPC: Resembles R_386_PC32, except that it uses the address of the global offset table in its calculation. The symbol referenced in this relocation normally is _GLOBAL_OFFSET_TABLE_, which also instructs the link-editor to create the global offset table.