Lines Matching full:relocation
273 Each canonical BFD relocation record contains a pointer to the
275 section the data is in, and a pointer to a relocation type
276 descriptor. Relocation is performed by passing messages through
277 the relocation type descriptor and the symbol pointer. Therefore,
278 relocations can be performed on output data using a relocation
280 instance, Oasys provides a byte relocation format. A relocation
281 record requesting this relocation type would point indirectly to a
282 routine to perform this, so the relocation may be performed on a
284 such relocation type.
372 /* BFD contains relocation entries. */
703 Return the number of bytes required to store the relocation information
715 external form of the relocation information attached to SEC into the
729 Set the relocation pointer and count within section SEC to the values
1289 contain raw data in sections, but data and relocation expressions
1394 some relocation information too. */
1414 the symbol to it, and builds a relocation. To build the lists
1465 the symbol and addend values specified by the associated relocation
1466 entries. Entries without associated relocation entries will be
1500 relocation or other arcane processing. It is skipped when
1653 /* If an input section, a pointer to a vector of relocation
1655 struct reloc_cache_entry *relocation;
1658 relocation records for the data in this section. */
1661 /* The number of relocation records in one of the above. */
1670 /* File position of relocation info. */
1878 /* relocation, orelocation, reloc_count, filepos, rel_filepos, */ \
2441 /* This symbol represents a complex relocation expression,
2445 /* This symbol represents a signed complex relocation expression,
2831 a `struct reloc_cache_entry' for each relocation in a particular
2845 This is the structure of a relocation entry:
2853 /* The relocation was performed, but there was an overflow. */
2862 /* Unsupported relocation size requested. */
2871 /* The relocation was performed, but may not be ok - presently
2888 /* addend for relocation value. */
2891 /* Pointer to how to perform the required relocation. */
2901 associated with the relocation request. It is the pointer into the
2905 by modifying only one pointer. The relocation routine looks in the
2907 the value of the symbol as the initial relocation offset. If the symbol
2912 section data which owns the relocation record to the first byte of
2914 this point; for example, a relocation type which modifies the bottom
2920 the relocation offset. Its interpretation is dependent upon the howto.
2940 RELOCATION RECORDS FOR [.text]:
2961 RELOCATION RECORDS FOR [.text]:
2970 The relocation routine digs out the value from the data, adds it to
2990 RELOCATION RECORDS FOR [.text]:
3002 The `howto' field can be imagined as a relocation instruction. It is
3005 back end would normally have a relocation instruction set and turn
3013 a relocation.
3048 in this field. For example, a PC relative word relocation
3053 /* The value the final relocation is shifted right by. This drops
3054 unwanted data from the relocation. */
3059 on by a type of relocation, use bfd_get_reloc_size. */
3066 /* Notes that the relocation is relative to the location in the
3067 data section of the addend. The relocation function will
3068 subtract from the relocation value the address of the location
3082 strange relocation methods to be accommodated (e.g., i960 callj
3088 /* The textual name of the relocation type. */
3091 /* Some formats record a relocation addend in the section contents
3092 rather than with the relocation. For ELF formats this is the
3098 recorded with the relocation (in arelent.addend); when performing
3099 a partial link the relocation will be modified.
3109 in the relocation sum. If the target relocations don't have an
3124 slot of the instruction, so that a PC relative relocation can
3153 Helper routine to turn a symbol into a relocation value.
3154 #define HOWTO_PREPARE(relocation, symbol) \
3160 relocation = 0; \
3164 relocation = symbol->value; \
3199 bfd_vma relocation);
3201 Perform overflow checking on RELOCATION which has BITSIZE significant
3222 modifying the output data in place, and by modifying the relocation
3224 way of specifying an addend in the relocation type, so the addend has
3244 suitable for use when creating, rather than applying a relocation.
3255 When an application wants to create a relocation, but doesn't know what
3264 be one enumerator for every type of relocation we ever do. Pass one of
3290 address of the relocation itself; sometimes they are relative to
3291 the start of the section containing the relocation. It depends on
3294 The 24-bit relocation is used in some Intel 960 configurations.
3352 Absolute 8-bit relocation, but used to form an address like 0xFFnn.
3372 displacements off that register. These relocation types are
3404 relocation types already defined.
3437 SPARC little endian relocation
3497 The ELF GPDISP relocation is exactly the same as the GPDISP_HI16
3498 relocation except that there is no accompanying GPDISP_LO16
3499 relocation.
3529 The HINT relocation indicates a value that should be filled into
3534 The LINKAGE relocation outputs a linkage pair in the object file,
3538 The CODEADDR relocation outputs a STO_CA in the object file, which
3552 The NOP relocation outputs a NOP if the longword displacement
3556 The BSR relocation outputs a BSR if the longword displacement
3560 The LDA relocation outputs a LDA if the longword displacement
3564 The BOH relocation outputs a BSR if the longword displacement
3583 Bits 27..2 of the relocation address shifted right 2 bits; simple
3631 Relocation against a MIPS literal section.
3938 probably a 32 bit wide absolute relocation, but the target can
3939 choose. It generally does map to one of the other relocation
3984 Pc-relative or absolute relocation depending on target. Used for
3996 may be a pc-relative or some form of GOT-indirect relocation.
4244 ADI Blackfin GOT relocation.
4247 ADI Blackfin PLTPC relocation.
4250 ADI Blackfin arithmetic relocation.
4253 ADI Blackfin arithmetic relocation.
4256 ADI Blackfin arithmetic relocation.
4259 ADI Blackfin arithmetic relocation.
4262 ADI Blackfin arithmetic relocation.
4265 ADI Blackfin arithmetic relocation.
4268 ADI Blackfin arithmetic relocation.
4271 ADI Blackfin arithmetic relocation.
4274 ADI Blackfin arithmetic relocation.
4277 ADI Blackfin arithmetic relocation.
4280 ADI Blackfin arithmetic relocation.
4283 ADI Blackfin arithmetic relocation.
4286 ADI Blackfin arithmetic relocation.
4289 ADI Blackfin arithmetic relocation.
4292 ADI Blackfin arithmetic relocation.
4295 ADI Blackfin arithmetic relocation.
4298 ADI Blackfin arithmetic relocation.
4301 ADI Blackfin arithmetic relocation.
4304 ADI Blackfin arithmetic relocation.
4307 ADI Blackfin arithmetic relocation.
4622 This is a relocation for a relative address as in a GETA
4626 This is a relocation for a relative address as in a JMP
4630 This is a relocation for an instruction field that may be a general
4634 This is a relocation for an instruction field that may be a general
4638 This is a relocation for two instruction fields holding a register
4639 and an offset, the equivalent of the relocation.
4642 This relocation is an assertion that the expression is not
4953 VTABLE_INHERIT is a zero-space relocation used to describe to the
4955 relocation's symbol should be the parent class' vtable, and the
4956 relocation should be located at the child vtable.
4958 VTABLE_ENTRY is a zero-space relocation that describes the use of a
5226 relocation.
5308 Morpho MT - 16 bit immediate relocation.
5323 Morpho MT - 8 bit immediate relocation.
5332 msp430 specific relocation codes
5340 Special Xtensa relocation used only by PLT entries in ELF shared
5350 Xtensa relocation used in ELF object files for symbols that may
5352 relocation.
5360 difference assuming no relaxation. The relocation encodes the
5380 number is encoded in the relocation. The relocation applies to the
5400 relocation. The meaning of these relocations is opcode-specific.
5409 Xtensa relocation to mark that the assembler expanded the
5414 Xtensa relocation to mark that the linker should simplify
5455 Pair of relocation. Contains the first symbol.
5506 two words (with an imm instruction). No relocation is done here -
5511 two words (with an imm instruction). The relocation is
5516 two words (with an imm instruction). The relocation is GOT offset
5520 two words (with an imm instruction). The relocation is
5525 in two words (with an imm instruction). The relocation is
5530 in a word. The relocation is relative offset from
5549 the relocation CODE on data from the architecture noted.
5558 Provides a default relocation lookup routine for any architecture.
5566 Provides a printable name for the supplied relocation code. Useful
5614 Provides default handling of relocation effort for back ends which
7714 include information about the symbol the relocation is against and a
7715 `reloc_howto_type' argument which describes the relocation to perform.
7719 section contents is `aout_link_input_section'. The actual relocation
8095 shape of the relocation information.
8173 forms of a.out relocation records.
8344 includes `coffcode.h'. Since the i960 has complex relocation types,
8880 relocation table and create an `internal_reloc'. The symbol index to
8883 the relocation offset; the type is dug directly from the howto field.
8913 Reading a coff relocation table is done in the following stages:
8915 * Read the entire coff relocation table into memory.
8917 * Process each relocation in turn; first swap it from the external
8920 * Turn the symbol referenced in the relocation's symbol index into a
