• Home
  • History
  • Annotate
  • Raw
  • Download
  • only in /asuswrt-rt-n18u-9.0.0.4.380.2695/release/src/router/gdb/bfd/

Lines Matching refs:relocation

1 /* BFD support for handling relocation entries.
38 a <<struct reloc_cache_entry>> for each relocation
63 This is the structure of a relocation entry:
72 . {* The relocation was performed, but there was an overflow. *}
81 . {* Unsupported relocation size requested. *}
90 . {* The relocation was performed, but may not be ok - presently
107 . {* addend for relocation value. *}
110 . {* Pointer to how to perform the required relocation. *}
126 associated with the relocation request. It is the pointer
131 modifying only one pointer. The relocation routine looks in
134 relocation offset. If the symbol pointer is zero, then the
140 the section data which owns the relocation record to the first
142 will be relative to this point; for example, a relocation
150 to the relocation offset. Its interpretation is dependent upon
200 The relocation routine digs out the value from the data, adds
236 relocation instruction. It is a pointer to a structure which
239 would normally have a relocation instruction set and turn
250 performing a relocation.
290 . in this field. For example, a PC relative word relocation
295 . {* The value the final relocation is shifted right by. This drops
296 . unwanted data from the relocation. *}
301 . on by a type of relocation, use bfd_get_reloc_size. *}
308 . {* Notes that the relocation is relative to the location in the
309 . data section of the addend. The relocation function will
310 . subtract from the relocation value the address of the location
324 . strange relocation methods to be accommodated (e.g., i960 callj
330 . {* The textual name of the relocation type. *}
333 . {* Some formats record a relocation addend in the section contents
334 . rather than with the relocation. For ELF formats this is the
340 . recorded with the relocation (in arelent.addend); when performing
341 . a partial link the relocation will be modified.
351 . in the relocation sum. If the target relocations don't have an
366 . slot of the instruction, so that a PC relative relocation can
403 Helper routine to turn a symbol into a relocation value.
405 .#define HOWTO_PREPARE(relocation, symbol) \
411 . relocation = 0; \
415 . relocation = symbol->value; \
480 bfd_vma relocation);
483 Perform overflow checking on @var{relocation} which has
496 bfd_vma relocation)
508 a = (relocation & addrmask) >> rightshift;;
565 relocation record. Some native formats (e.g., basic a.out and
567 relocation type, so the addend has to go in the output data.
584 bfd_vma relocation;
608 /* If there is a function supplied to handle this relocation type,
621 /* Is the address of the relocation really within the section? */
625 /* Work out which section the relocation is targeted at and the
626 initial relocation command value. */
630 relocation = 0;
632 relocation = symbol->value;
643 relocation += output_base + symbol->section->output_offset;
646 relocation += reloc_entry->addend;
648 /* Here the variable relocation holds the final address of the
653 /* This is a PC relative relocation. We want to set RELOCATION
670 relocation is done. If pcrel_offset is FALSE we want to wind
681 relocation -=
685 relocation -= reloc_entry->address;
692 /* This is a partial relocation, and we want to apply the relocation
695 reloc_entry->addend = relocation;
701 /* This is a partial relocation, but inplace, so modify the
715 relocation with -r. Removing the line below this comment
783 relocation -= reloc_entry->addend;
788 reloc_entry->addend = relocation;
810 relocation);
813 the relocation to the reloc entry (probably because there isn't
839 relocation >>= (bfd_vma) howto->rightshift;
842 relocation <<= (bfd_vma) howto->bitpos;
849 r relocation offset to apply
878 x = ( (x & ~howto->dst_mask) | (((x & howto->src_mask) + relocation) & howto->dst_mask))
907 relocation = -relocation;
916 relocation = -relocation;
960 a relocation.
974 bfd_vma relocation;
990 /* If there is a function supplied to handle this relocation type,
1008 /* Is the address of the relocation really within the section? */
1012 /* Work out which section the relocation is targeted at and the
1013 initial relocation command value. */
1017 relocation = 0;
1019 relocation = symbol->value;
1029 relocation += output_base + symbol->section->output_offset;
1032 relocation += reloc_entry->addend;
1034 /* Here the variable relocation holds the final address of the
1039 /* This is a PC relative relocation. We want to set RELOCATION
1056 relocation is done. If pcrel_offset is FALSE we want to wind
1067 relocation -=
1071 relocation -= reloc_entry->address;
1076 /* This is a partial relocation, and we want to apply the relocation
1079 reloc_entry->addend = relocation;
1085 /* This is a partial relocation, but inplace, so modify the
1099 relocation with -r. Removing the line below this comment
1166 relocation -= reloc_entry->addend;
1173 reloc_entry->addend = relocation;
1189 relocation);
1192 the relocation to the reloc entry (probably because there isn't
1218 relocation >>= (bfd_vma) howto->rightshift;
1221 relocation <<= (bfd_vma) howto->bitpos;
1228 r relocation offset to apply
1257 x = ( (x & ~howto->dst_mask) | (((x & howto->src_mask) + relocation) & howto->dst_mask))
1288 relocation = -relocation;
1312 /* This relocation routine is used by some of the backend linkers.
1318 This routine does a final relocation. Whether it is useful for a
1343 bfd_vma relocation;
1349 /* This function assumes that we are dealing with a basic relocation
1353 relocation = value + addend;
1355 /* If the relocation is PC relative, we want to set RELOCATION to
1367 relocation -= (input_section->output_section->vma
1370 relocation -= address;
1373 return _bfd_relocate_contents (howto, input_bfd, relocation,
1382 bfd_vma relocation,
1394 relocation = -relocation;
1438 a = (relocation & addrmask) >> rightshift;
1515 relocation >>= (bfd_vma) rightshift;
1516 relocation <<= (bfd_vma) bitpos;
1520 | (((x & howto->src_mask) + relocation) & howto->dst_mask));
1548 /* Clear a given location using a given howto, by applying a relocation value
1622 When an application wants to create a relocation, but doesn't
1634 will be one enumerator for every type of relocation we ever do.
1676 of the relocation itself; sometimes they are relative to the start of
1677 the section containing the relocation. It depends on the specific target.
1679 The 24-bit relocation is used in some Intel 960 configurations.
1760 Absolute 8-bit relocation, but used to form an address like 0xFFnn.
1790 displacements off that register. These relocation types are
1835 relocation types already defined.
1900 SPARC little endian relocation
2003 The ELF GPDISP relocation is exactly the same as the GPDISP_HI16
2004 relocation except that there is no accompanying GPDISP_LO16
2005 relocation.
2041 The HINT relocation indicates a value that should be filled into the
2048 The LINKAGE relocation outputs a linkage pair in the object file,
2054 The CODEADDR relocation outputs a STO_CA in the object file,
2104 Bits 27..2 of the relocation address shifted right 2 bits;
2720 probably a 32 bit wide absolute relocation, but the target can choose.
2721 It generally does map to one of the other relocation types.
2781 Pc-relative or absolute relocation depending on target. Used for
2796 pc-relative or some form of GOT-indirect relocation.
3243 ADI Blackfin GOT relocation.
3247 ADI Blackfin PLTPC relocation.
3251 ADI Blackfin arithmetic relocation.
3255 ADI Blackfin arithmetic relocation.
3259 ADI Blackfin arithmetic relocation.
3263 ADI Blackfin arithmetic relocation.
3267 ADI Blackfin arithmetic relocation.
3271 ADI Blackfin arithmetic relocation.
3275 ADI Blackfin arithmetic relocation.
3279 ADI Blackfin arithmetic relocation.
3283 ADI Blackfin arithmetic relocation.
3287 ADI Blackfin arithmetic relocation.
3291 ADI Blackfin arithmetic relocation.
3295 ADI Blackfin arithmetic relocation.
3299 ADI Blackfin arithmetic relocation.
3303 ADI Blackfin arithmetic relocation.
3307 ADI Blackfin arithmetic relocation.
3311 ADI Blackfin arithmetic relocation.
3315 ADI Blackfin arithmetic relocation.
3319 ADI Blackfin arithmetic relocation.
3323 ADI Blackfin arithmetic relocation.
3327 ADI Blackfin arithmetic relocation.
3799 This is a relocation for a relative address as in a GETA instruction or
3804 This is a relocation for a relative address as in a JMP instruction.
3808 This is a relocation for an instruction field that may be a general
3813 This is a relocation for an instruction field that may be a general
3818 This is a relocation for two instruction fields holding a register and
3819 an offset, the equivalent of the relocation.
3823 This relocation is an assertion that the expression is not allocated as
4206 VTABLE_INHERIT is a zero-space relocation used to describe to the
4208 relocation's symbol should be the parent class' vtable, and the
4209 relocation should be located at the child vtable.
4211 VTABLE_ENTRY is a zero-space relocation that describes the use of a
4679 32-bit offset to symbol with PLT entry, relative to this relocation.
4808 Morpho MT - 16 bit immediate relocation.
4828 Morpho MT - 8 bit immediate relocation.
4845 msp430 specific relocation codes
4859 Special Xtensa relocation used only by PLT entries in ELF shared
4873 Xtensa relocation used in ELF object files for symbols that may require
4874 PLT entries. Otherwise, this is just a generic 32-bit relocation.
4885 assuming no relaxation. The relocation encodes the position of the
4920 number is encoded in the relocation. The relocation applies to the
4955 relocation. The meaning of these relocations is opcode-specific.
4968 Xtensa relocation to mark that the assembler expanded the
4974 Xtensa relocation to mark that the linker should simplify
5017 invoked, will perform the relocation @var{code} on data from the
5046 Provides a default relocation lookup routine for any architecture.
5083 Provides a printable name for the supplied relocation code.
5175 Provides default handling of relocation effort for back ends