Home | History | Annotate | Download | only in info

Lines Matching full:addend

1465           the symbol and addend values specified by the associated relocation
2888 /* addend for relocation value. */
2889 bfd_vma addend;
2918 * `addend'
2919 The `addend' is a value provided by the back end to be added (!) to
2959 0x12340000 in their addend field. The data would consist of:
2971 the addend to get the original offset, and then adds the value of
3067 data section of the addend. The relocation function will
3091 /* Some formats record a relocation addend in the section contents
3095 addend is recorded with the section contents; when performing a
3098 recorded with the relocation (in arelent.addend); when performing
3110 addend in the reloc, eg. ELF USE_REL, src_mask will normally equal
3111 dst_mask to extract the addend from the section contents. If
3112 relocations do have an addend in the reloc, eg. ELF USE_RELA, this
3224 way of specifying an addend in the relocation type, so the addend has
3226 the output data slot will always be big enough for the addend. Complex
3484 "addend" in some special way. For GPDISP_HI16 ("gpdisp")
3486 will be the absolute section symbol. The addend is the
3492 with GPDISP_HI16 relocs. The addend is ignored when writing the
3510 section symbol. The addend is ignored when writing, but is filled
3523 ignored (read as the absolute section symbol), and the "addend"
3750 The addend of this reloc is an alignment power that must be
4962 this offset is stored in the reloc's addend. For Rel hosts, we
5476 Same as BFD_RELOC_32_PCREL but with an implicit -1 addend.
5479 Same as BFD_RELOC_32_PCREL but with an implicit -2 addend.
5482 Same as BFD_RELOC_32_PCREL but with an implicit -4 addend.
8177 full integer for an addend.
8930 addend field.