Lines Matching full:relocation
274 Each canonical BFD relocation record contains a pointer to the
276 section the data is in, and a pointer to a relocation type
277 descriptor. Relocation is performed by passing messages through
278 the relocation type descriptor and the symbol pointer. Therefore,
279 relocations can be performed on output data using a relocation
281 instance, Oasys provides a byte relocation format. A relocation
282 record requesting this relocation type would point indirectly to a
283 routine to perform this, so the relocation may be performed on a
285 such relocation type.
373 /* BFD contains relocation entries. */
723 Return the number of bytes required to store the relocation information
735 external form of the relocation information attached to SEC into the
749 Set the relocation pointer and count within section SEC to the values
1310 contain raw data in sections, but data and relocation expressions
1415 some relocation information too. */
1435 the symbol to it, and builds a relocation. To build the lists
1486 the symbol and addend values specified by the associated relocation
1487 entries. Entries without associated relocation entries will be
1521 relocation or other arcane processing. It is skipped when
1683 /* If an input section, a pointer to a vector of relocation
1685 struct reloc_cache_entry *relocation;
1688 relocation records for the data in this section. */
1691 /* The number of relocation records in one of the above. */
1700 /* File position of relocation info. */
1908 /* relocation, orelocation, reloc_count, filepos, rel_filepos, */ \
2480 /* This symbol represents a complex relocation expression,
2484 /* This symbol represents a signed complex relocation expression,
2870 a `struct reloc_cache_entry' for each relocation in a particular
2884 This is the structure of a relocation entry:
2892 /* The relocation was performed, but there was an overflow. */
2901 /* Unsupported relocation size requested. */
2910 /* The relocation was performed, but may not be ok - presently
2927 /* addend for relocation value. */
2930 /* Pointer to how to perform the required relocation. */
2940 associated with the relocation request. It is the pointer into the
2944 by modifying only one pointer. The relocation routine looks in the
2946 the value of the symbol as the initial relocation offset. If the symbol
2951 section data which owns the relocation record to the first byte of
2953 this point; for example, a relocation type which modifies the bottom
2959 the relocation offset. Its interpretation is dependent upon the howto.
2979 RELOCATION RECORDS FOR [.text]:
3000 RELOCATION RECORDS FOR [.text]:
3009 The relocation routine digs out the value from the data, adds it to
3029 RELOCATION RECORDS FOR [.text]:
3041 The `howto' field can be imagined as a relocation instruction. It is
3044 back end would normally have a relocation instruction set and turn
3052 a relocation.
3087 in this field. For example, a PC relative word relocation
3092 /* The value the final relocation is shifted right by. This drops
3093 unwanted data from the relocation. */
3098 on by a type of relocation, use bfd_get_reloc_size. */
3105 /* The relocation is relative to the field being relocated. */
3118 strange relocation methods to be accommodated (e.g., i960 callj
3124 /* The textual name of the relocation type. */
3127 /* Some formats record a relocation addend in the section contents
3128 rather than with the relocation. For ELF formats this is the
3134 recorded with the relocation (in arelent.addend); when performing
3135 a partial link the relocation will be modified.
3145 in the relocation sum. If the target relocations don't have an
3160 slot of the instruction, so that a PC relative relocation can
3189 Helper routine to turn a symbol into a relocation value.
3190 #define HOWTO_PREPARE(relocation, symbol) \
3196 relocation = 0; \
3200 relocation = symbol->value; \
3235 bfd_vma relocation);
3237 Perform overflow checking on RELOCATION which has BITSIZE significant
3258 modifying the output data in place, and by modifying the relocation
3260 way of specifying an addend in the relocation type, so the addend has
3280 suitable for use when creating, rather than applying a relocation.
3291 When an application wants to create a relocation, but doesn't know what
3300 be one enumerator for every type of relocation we ever do. Pass one of
3326 address of the relocation itself; sometimes they are relative to
3327 the start of the section containing the relocation. It depends on
3330 The 24-bit relocation is used in some Intel 960 configurations.
3388 Absolute 8-bit relocation, but used to form an address like 0xFFnn.
3408 displacements off that register. These relocation types are
3440 relocation types already defined.
3473 SPARC little endian relocation
3533 The ELF GPDISP relocation is exactly the same as the GPDISP_HI16
3534 relocation except that there is no accompanying GPDISP_LO16
3535 relocation.
3565 The HINT relocation indicates a value that should be filled into
3570 The LINKAGE relocation outputs a linkage pair in the object file,
3574 The CODEADDR relocation outputs a STO_CA in the object file, which
3588 The NOP relocation outputs a NOP if the longword displacement
3592 The BSR relocation outputs a BSR if the longword displacement
3596 The LDA relocation outputs a LDA if the longword displacement
3600 The BOH relocation outputs a BSR if the longword displacement
3619 Bits 27..2 of the relocation address shifted right 2 bits; simple
3667 Relocation against a MIPS literal section.
3974 probably a 32 bit wide absolute relocation, but the target can
3975 choose. It generally does map to one of the other relocation
4020 Pc-relative or absolute relocation depending on target. Used for
4032 may be a pc-relative or some form of GOT-indirect relocation.
4298 ADI Blackfin GOT relocation.
4301 ADI Blackfin PLTPC relocation.
4304 ADI Blackfin arithmetic relocation.
4307 ADI Blackfin arithmetic relocation.
4310 ADI Blackfin arithmetic relocation.
4313 ADI Blackfin arithmetic relocation.
4316 ADI Blackfin arithmetic relocation.
4319 ADI Blackfin arithmetic relocation.
4322 ADI Blackfin arithmetic relocation.
4325 ADI Blackfin arithmetic relocation.
4328 ADI Blackfin arithmetic relocation.
4331 ADI Blackfin arithmetic relocation.
4334 ADI Blackfin arithmetic relocation.
4337 ADI Blackfin arithmetic relocation.
4340 ADI Blackfin arithmetic relocation.
4343 ADI Blackfin arithmetic relocation.
4346 ADI Blackfin arithmetic relocation.
4349 ADI Blackfin arithmetic relocation.
4352 ADI Blackfin arithmetic relocation.
4355 ADI Blackfin arithmetic relocation.
4358 ADI Blackfin arithmetic relocation.
4361 ADI Blackfin arithmetic relocation.
4774 This is a relocation for a relative address as in a GETA
4778 This is a relocation for a relative address as in a JMP
4782 This is a relocation for an instruction field that may be a general
4786 This is a relocation for an instruction field that may be a general
4790 This is a relocation for two instruction fields holding a register
4791 and an offset, the equivalent of the relocation.
4794 This relocation is an assertion that the expression is not
5108 VTABLE_INHERIT is a zero-space relocation used to describe to the
5110 relocation's symbol should be the parent class' vtable, and the
5111 relocation should be located at the child vtable.
5113 VTABLE_ENTRY is a zero-space relocation that describes the use of a
5381 relocation.
5463 Morpho MT - 16 bit immediate relocation.
5478 Morpho MT - 8 bit immediate relocation.
5487 msp430 specific relocation codes
5495 Special Xtensa relocation used only by PLT entries in ELF shared
5505 Xtensa relocation used in ELF object files for symbols that may
5507 relocation.
5515 difference assuming no relaxation. The relocation encodes the
5535 number is encoded in the relocation. The relocation applies to the
5555 relocation. The meaning of these relocations is opcode-specific.
5564 Xtensa relocation to mark that the assembler expanded the
5569 Xtensa relocation
5610 Pair of relocation. Contains the first symbol.
5661 two words (with an imm instruction). No relocation is done here -
5666 two words (with an imm instruction). The relocation is
5671 two words (with an imm instruction). The relocation is GOT offset
5675 two words (with an imm instruction). The relocation is
5680 in two words (with an imm instruction). The relocation is
5685 in a word. The relocation is relative offset from
5704 the relocation CODE on data from the architecture noted.
5713 Provides a default relocation lookup routine for any architecture.
5721 Provides a printable name for the supplied relocation code. Useful
5769 Provides default handling of relocation effort for back ends which
7902 include information about the symbol the relocation is against and a
7903 `reloc_howto_type' argument which describes the relocation to perform.
7907 section contents is `aout_link_input_section'. The actual relocation
8283 shape of the relocation information.
8361 forms of a.out relocation records.
8532 includes `coffcode.h'. Since the i960 has complex relocation types,
9068 relocation table and create an `internal_reloc'. The symbol index to
9071 the relocation offset; the type is dug directly from the howto field.
9101 Reading a coff relocation table is done in the following stages:
9103 * Read the entire coff relocation table into memory.
9105 * Process each relocation in turn; first swap it from the external
9108 * Turn the symbol referenced in the relocation's symbol index into a
