Lines Matching full:relocation
272 Each canonical BFD relocation record contains a pointer to the
274 section the data is in, and a pointer to a relocation type
275 descriptor. Relocation is performed by passing messages through
276 the relocation type descriptor and the symbol pointer. Therefore,
277 relocations can be performed on output data using a relocation
279 instance, Oasys provides a byte relocation format. A relocation
280 record requesting this relocation type would point indirectly to a
281 routine to perform this, so the relocation may be performed on a
283 such relocation type.
371 /* BFD contains relocation entries. */
702 Return the number of bytes required to store the relocation information
714 external form of the relocation information attached to SEC into the
728 Set the relocation pointer and count within section SEC to the values
1288 contain raw data in sections, but data and relocation expressions
1393 some relocation information too. */
1413 the symbol to it, and builds a relocation. To build the lists
1464 the symbol and addend values specified by the associated relocation
1465 entries. Entries without associated relocation entries will be
1499 relocation or other arcane processing. It is skipped when
1652 /* If an input section, a pointer to a vector of relocation
1654 struct reloc_cache_entry *relocation;
1657 relocation records for the data in this section. */
1660 /* The number of relocation records in one of the above. */
1669 /* File position of relocation info. */
1877 /* relocation, orelocation, reloc_count, filepos, rel_filepos, */ \
2440 /* This symbol represents a complex relocation expression,
2444 /* This symbol represents a signed complex relocation expression,
2830 a `struct reloc_cache_entry' for each relocation in a particular
2844 This is the structure of a relocation entry:
2852 /* The relocation was performed, but there was an overflow. */
2861 /* Unsupported relocation size requested. */
2870 /* The relocation was performed, but may not be ok - presently
2887 /* addend for relocation value. */
2890 /* Pointer to how to perform the required relocation. */
2900 associated with the relocation request. It is the pointer into the
2904 by modifying only one pointer. The relocation routine looks in the
2906 the value of the symbol as the initial relocation offset. If the symbol
2911 section data which owns the relocation record to the first byte of
2913 this point; for example, a relocation type which modifies the bottom
2919 the relocation offset. Its interpretation is dependent upon the howto.
2939 RELOCATION RECORDS FOR [.text]:
2960 RELOCATION RECORDS FOR [.text]:
2969 The relocation routine digs out the value from the data, adds it to
2989 RELOCATION RECORDS FOR [.text]:
3001 The `howto' field can be imagined as a relocation instruction. It is
3004 back end would normally have a relocation instruction set and turn
3012 a relocation.
3047 in this field. For example, a PC relative word relocation
3052 /* The value the final relocation is shifted right by. This drops
3053 unwanted data from the relocation. */
3058 on by a type of relocation, use bfd_get_reloc_size. */
3065 /* Notes that the relocation is relative to the location in the
3066 data section of the addend. The relocation function will
3067 subtract from the relocation value the address of the location
3081 strange relocation methods to be accommodated (e.g., i960 callj
3087 /* The textual name of the relocation type. */
3090 /* Some formats record a relocation addend in the section contents
3091 rather than with the relocation. For ELF formats this is the
3097 recorded with the relocation (in arelent.addend); when performing
3098 a partial link the relocation will be modified.
3108 in the relocation sum. If the target relocations don't have an
3123 slot of the instruction, so that a PC relative relocation can
3152 Helper routine to turn a symbol into a relocation value.
3153 #define HOWTO_PREPARE(relocation, symbol) \
3159 relocation = 0; \
3163 relocation = symbol->value; \
3198 bfd_vma relocation);
3200 Perform overflow checking on RELOCATION which has BITSIZE significant
3221 modifying the output data in place, and by modifying the relocation
3223 way of specifying an addend in the relocation type, so the addend has
3243 suitable for use when creating, rather than applying a relocation.
3254 When an application wants to create a relocation, but doesn't know what
3263 be one enumerator for every type of relocation we ever do. Pass one of
3289 address of the relocation itself; sometimes they are relative to
3290 the start of the section containing the relocation. It depends on
3293 The 24-bit relocation is used in some Intel 960 configurations.
3351 Absolute 8-bit relocation, but used to form an address like 0xFFnn.
3371 displacements off that register. These relocation types are
3403 relocation types already defined.
3436 SPARC little endian relocation
3496 The ELF GPDISP relocation is exactly the same as the GPDISP_HI16
3497 relocation except that there is no accompanying GPDISP_LO16
3498 relocation.
3528 The HINT relocation indicates a value that should be filled into
3533 The LINKAGE relocation outputs a linkage pair in the object file,
3537 The CODEADDR relocation outputs a STO_CA in the object file, which
3551 The NOP relocation outputs a NOP if the longword displacement
3555 The BSR relocation outputs a BSR if the longword displacement
3559 The LDA relocation outputs a LDA if the longword displacement
3563 The BOH relocation outputs a BSR if the longword displacement
3582 Bits 27..2 of the relocation address shifted right 2 bits; simple
3630 Relocation against a MIPS literal section.
3937 probably a 32 bit wide absolute relocation, but the target can
3938 choose. It generally does map to one of the other relocation
3983 Pc-relative or absolute relocation depending on target. Used for
3995 may be a pc-relative or some form of GOT-indirect relocation.
4243 ADI Blackfin GOT relocation.
4246 ADI Blackfin PLTPC relocation.
4249 ADI Blackfin arithmetic relocation.
4252 ADI Blackfin arithmetic relocation.
4255 ADI Blackfin arithmetic relocation.
4258 ADI Blackfin arithmetic relocation.
4261 ADI Blackfin arithmetic relocation.
4264 ADI Blackfin arithmetic relocation.
4267 ADI Blackfin arithmetic relocation.
4270 ADI Blackfin arithmetic relocation.
4273 ADI Blackfin arithmetic relocation.
4276 ADI Blackfin arithmetic relocation.
4279 ADI Blackfin arithmetic relocation.
4282 ADI Blackfin arithmetic relocation.
4285 ADI Blackfin arithmetic relocation.
4288 ADI Blackfin arithmetic relocation.
4291 ADI Blackfin arithmetic relocation.
4294 ADI Blackfin arithmetic relocation.
4297 ADI Blackfin arithmetic relocation.
4300 ADI Blackfin arithmetic relocation.
4303 ADI Blackfin arithmetic relocation.
4306 ADI Blackfin arithmetic relocation.
4621 This is a relocation for a relative address as in a GETA
4625 This is a relocation for a relative address as in a JMP
4629 This is a relocation for an instruction field that may be a general
4633 This is a relocation for an instruction field that may be a general
4637 This is a relocation for two instruction fields holding a register
4638 and an offset, the equivalent of the relocation.
4641 This relocation is an assertion that the expression is not
4952 VTABLE_INHERIT is a zero-space relocation used to describe to the
4954 relocation's symbol should be the parent class' vtable, and the
4955 relocation should be located at the child vtable.
4957 VTABLE_ENTRY is a zero-space relocation that describes the use of a
5225 relocation.
5307 Morpho MT - 16 bit immediate relocation.
5322 Morpho MT - 8 bit immediate relocation.
5331 msp430 specific relocation codes
5339 Special Xtensa relocation used only by PLT entries in ELF shared
5349 Xtensa relocation used in ELF object files for symbols that may
5351 relocation.
5359 difference assuming no relaxation. The relocation encodes the
5379 number is encoded in the relocation. The relocation applies to the
5399 relocation. The meaning of these relocations is opcode-specific.
5408 Xtensa relocation to mark that the assembler expanded the
5413 Xtensa relocation to mark that the linker should simplify
5454 Pair of relocation. Contains the first symbol.
5505 two words (with an imm instruction). No relocation is done here -
5510 two words (with an imm instruction). The relocation is
5515 two words (with an imm instruction). The relocation is GOT offset
5519 two words (with an imm instruction). The relocation is
5524 in two words (with an imm instruction). The relocation is
5529 in a word. The relocation is relative offset from
5548 the relocation CODE on data from the architecture noted.
5557 Provides a default relocation lookup routine for any architecture.
5565 Provides a printable name for the supplied relocation code. Useful
5613 Provides default handling of relocation effort for back ends which
7713 include information about the symbol the relocation is against and a
7714 `reloc_howto_type' argument which describes the relocation to perform.
7718 section contents is `aout_link_input_section'. The actual relocation
8094 shape of the relocation information.
8172 forms of a.out relocation records.
8343 includes `coffcode.h'. Since the i960 has complex relocation types,
8879 relocation table and create an `internal_reloc'. The symbol index to
8882 the relocation offset; the type is dug directly from the howto field.
8912 Reading a coff relocation table is done in the following stages:
8914 * Read the entire coff relocation table into memory.
8916 * Process each relocation in turn; first swap it from the external
8919 * Turn the symbol referenced in the relocation's symbol index into a
