Subversion Repositories openrisc

@section Relocations

BFD maintains relocations in much the same way it maintains

symbols: they are left alone until required, then read in

en-masse and translated into an internal form.  A common

routine @code{bfd_perform_relocation} acts upon the

canonical form to do the fixup.

Relocations are maintained on a per section basis,

while symbols are maintained on a per BFD basis.

All that a back end has to do to fit the BFD interface is to create

a @code{struct reloc_cache_entry} for each relocation

in a particular section, and fill in the right bits of the structures.

@menu

* typedef arelent::

* howto manager::

@end menu

@node typedef arelent, howto manager, Relocations, Relocations

@subsection typedef arelent

This is the structure of a relocation entry:

@example

typedef enum bfd_reloc_status

@{

  /* No errors detected.  */

  bfd_reloc_ok,

  /* The relocation was performed, but there was an overflow.  */

  bfd_reloc_overflow,

  /* The address to relocate was not within the section supplied.  */

  bfd_reloc_outofrange,

  /* Used by special functions.  */

  bfd_reloc_continue,

  /* Unsupported relocation size requested.  */

  bfd_reloc_notsupported,

  /* Unused.  */

  bfd_reloc_other,

  /* The symbol to relocate against was undefined.  */

  bfd_reloc_undefined,

  /* The relocation was performed, but may not be ok - presently

     generated only when linking i960 coff files with i960 b.out

     symbols.  If this type is returned, the error_message argument

     to bfd_perform_relocation will be set.  */

  bfd_reloc_dangerous

 @}

 bfd_reloc_status_type;

typedef struct reloc_cache_entry

@{

  /* A pointer into the canonical table of pointers.  */

  struct bfd_symbol **sym_ptr_ptr;

  /* offset in section.  */

  bfd_size_type address;

  /* addend for relocation value.  */

  bfd_vma addend;

  /* Pointer to how to perform the required relocation.  */

  reloc_howto_type *howto;

@}

arelent;

@end example

@strong{Description}@*

Here is a description of each of the fields within an @code{arelent}:

@itemize @bullet

@item

@code{sym_ptr_ptr}

@end itemize

The symbol table pointer points to a pointer to the symbol

associated with the relocation request.  It is the pointer

into the table returned by the back end's

@code{canonicalize_symtab} action. @xref{Symbols}. The symbol is

referenced through a pointer to a pointer so that tools like

the linker can fix up all the symbols of the same name by

modifying only one pointer. The relocation routine looks in

the symbol and uses the base of the section the symbol is

attached to and the value of the symbol as the initial

relocation offset. If the symbol pointer is zero, then the

section provided is looked up.

@itemize @bullet

@item

@code{address}

@end itemize

The @code{address} field gives the offset in bytes from the base of

the section data which owns the relocation record to the first

byte of relocatable information. The actual data relocated

will be relative to this point; for example, a relocation

type which modifies the bottom two bytes of a four byte word

would not touch the first byte pointed to in a big endian

world.

@itemize @bullet

@item

@code{addend}

@end itemize

The @code{addend} is a value provided by the back end to be added (!)

to the relocation offset. Its interpretation is dependent upon

the howto. For example, on the 68k the code:

@example

        char foo[];

        main()

                @{

                return foo[0x12345678];

                @}

@end example

Could be compiled into:

@example

        linkw fp,#-4

        moveb @@#12345678,d0

        extbl d0

        unlk fp

        rts

@end example

This could create a reloc pointing to @code{foo}, but leave the

offset in the data, something like:

@example

RELOCATION RECORDS FOR [.text]:

offset   type      value

00000006 32        _foo

00000000 4e56 fffc          ; linkw fp,#-4

00000004 1039 1234 5678     ; moveb @@#12345678,d0

0000000a 49c0               ; extbl d0

0000000c 4e5e               ; unlk fp

0000000e 4e75               ; rts

@end example

Using coff and an 88k, some instructions don't have enough

space in them to represent the full address range, and

pointers have to be loaded in two parts. So you'd get something like:

@example

        or.u     r13,r0,hi16(_foo+0x12345678)

        ld.b     r2,r13,lo16(_foo+0x12345678)

        jmp      r1

@end example

This should create two relocs, both pointing to @code{_foo}, and with

0x12340000 in their addend field. The data would consist of:

@example

RELOCATION RECORDS FOR [.text]:

offset   type      value

00000002 HVRT16    _foo+0x12340000

00000006 LVRT16    _foo+0x12340000

00000000 5da05678           ; or.u r13,r0,0x5678

00000004 1c4d5678           ; ld.b r2,r13,0x5678

00000008 f400c001           ; jmp r1

@end example

The relocation routine digs out the value from the data, adds

it to the addend to get the original offset, and then adds the

value of @code{_foo}. Note that all 32 bits have to be kept around

somewhere, to cope with carry from bit 15 to bit 16.

One further example is the sparc and the a.out format. The

sparc has a similar problem to the 88k, in that some

instructions don't have room for an entire offset, but on the

sparc the parts are created in odd sized lumps. The designers of

the a.out format chose to not use the data within the section

for storing part of the offset; all the offset is kept within

the reloc. Anything in the data should be ignored.

@example

        save %sp,-112,%sp

        sethi %hi(_foo+0x12345678),%g2

        ldsb [%g2+%lo(_foo+0x12345678)],%i0

        ret

        restore

@end example

Both relocs contain a pointer to @code{foo}, and the offsets

contain junk.

@example

RELOCATION RECORDS FOR [.text]:

offset   type      value

00000004 HI22      _foo+0x12345678

00000008 LO10      _foo+0x12345678

00000000 9de3bf90     ; save %sp,-112,%sp

00000004 05000000     ; sethi %hi(_foo+0),%g2

00000008 f048a000     ; ldsb [%g2+%lo(_foo+0)],%i0

0000000c 81c7e008     ; ret

00000010 81e80000     ; restore

@end example

@itemize @bullet

@item

@code{howto}

@end itemize

The @code{howto} field can be imagined as a

relocation instruction. It is a pointer to a structure which

contains information on what to do with all of the other

information in the reloc record and data section. A back end

would normally have a relocation instruction set and turn

relocations into pointers to the correct structure on input -

but it would be possible to create each howto field on demand.

@subsubsection @code{enum complain_overflow}

Indicates what sort of overflow checking should be done when

performing a relocation.

@example

enum complain_overflow

@{

  /* Do not complain on overflow.  */

  complain_overflow_dont,

  /* Complain if the value overflows when considered as a signed

     number one bit larger than the field.  ie. A bitfield of N bits

     is allowed to represent -2**n to 2**n-1.  */

  complain_overflow_bitfield,

  /* Complain if the value overflows when considered as a signed

     number.  */

  complain_overflow_signed,

  /* Complain if the value overflows when considered as an

     unsigned number.  */

  complain_overflow_unsigned

@};

@end example

@subsubsection @code{reloc_howto_type}

The @code{reloc_howto_type} is a structure which contains all the

information that libbfd needs to know to tie up a back end's data.

@example

struct bfd_symbol;             /* Forward declaration.  */

struct reloc_howto_struct

@{

  /*  The type field has mainly a documentary use - the back end can

      do what it wants with it, though normally the back end's

      external idea of what a reloc number is stored

      in this field.  For example, a PC relative word relocation

      in a coff environment has the type 023 - because that's

      what the outside world calls a R_PCRWORD reloc.  */

  unsigned int type;

  /*  The value the final relocation is shifted right by.  This drops

      unwanted data from the relocation.  */

  unsigned int rightshift;

  /*  The size of the item to be relocated.  This is *not* a

      power-of-two measure.  To get the number of bytes operated

      on by a type of relocation, use bfd_get_reloc_size.  */

  int size;

  /*  The number of bits in the item to be relocated.  This is used

      when doing overflow checking.  */

  unsigned int bitsize;

  /*  The relocation is relative to the field being relocated.  */

  bfd_boolean pc_relative;

  /*  The bit position of the reloc value in the destination.

      The relocated value is left shifted by this amount.  */

  unsigned int bitpos;

  /* What type of overflow error should be checked for when

     relocating.  */

  enum complain_overflow complain_on_overflow;

  /* If this field is non null, then the supplied function is

     called rather than the normal function.  This allows really

     strange relocation methods to be accommodated (e.g., i960 callj

     instructions).  */

  bfd_reloc_status_type (*special_function)

    (bfd *, arelent *, struct bfd_symbol *, void *, asection *,

     bfd *, char **);

  /* The textual name of the relocation type.  */

  char *name;

  /* Some formats record a relocation addend in the section contents

     rather than with the relocation.  For ELF formats this is the

     distinction between USE_REL and USE_RELA (though the code checks

     for USE_REL == 1/0).  The value of this field is TRUE if the

     addend is recorded with the section contents; when performing a

     partial link (ld -r) the section contents (the data) will be

     modified.  The value of this field is FALSE if addends are

     recorded with the relocation (in arelent.addend); when performing

     a partial link the relocation will be modified.

     All relocations for all ELF USE_RELA targets should set this field

     to FALSE (values of TRUE should be looked on with suspicion).

     However, the converse is not true: not all relocations of all ELF

     USE_REL targets set this field to TRUE.  Why this is so is peculiar

     to each particular target.  For relocs that aren't used in partial

     links (e.g. GOT stuff) it doesn't matter what this is set to.  */

  bfd_boolean partial_inplace;

  /* src_mask selects the part of the instruction (or data) to be used

     in the relocation sum.  If the target relocations don't have an

     addend in the reloc, eg. ELF USE_REL, src_mask will normally equal

     dst_mask to extract the addend from the section contents.  If

     relocations do have an addend in the reloc, eg. ELF USE_RELA, this

     field should be zero.  Non-zero values for ELF USE_RELA targets are

     bogus as in those cases the value in the dst_mask part of the

     section contents should be treated as garbage.  */

  bfd_vma src_mask;

  /* dst_mask selects which parts of the instruction (or data) are

     replaced with a relocated value.  */

  bfd_vma dst_mask;

  /* When some formats create PC relative instructions, they leave

     the value of the pc of the place being relocated in the offset

     slot of the instruction, so that a PC relative relocation can

     be made just by adding in an ordinary offset (e.g., sun3 a.out).

     Some formats leave the displacement part of an instruction

     empty (e.g., m88k bcs); this flag signals the fact.  */

  bfd_boolean pcrel_offset;

@};

@end example

@findex The HOWTO Macro

@subsubsection @code{The HOWTO Macro}

@strong{Description}@*

The HOWTO define is horrible and will go away.

@example

#define HOWTO(C, R, S, B, P, BI, O, SF, NAME, INPLACE, MASKSRC, MASKDST, PC) \

  @{ (unsigned) C, R, S, B, P, BI, O, SF, NAME, INPLACE, MASKSRC, MASKDST, PC @}

@end example

@strong{Description}@*

And will be replaced with the totally magic way. But for the

moment, we are compatible, so do it this way.

@example

#define NEWHOWTO(FUNCTION, NAME, SIZE, REL, IN) \

  HOWTO (0, 0, SIZE, 0, REL, 0, complain_overflow_dont, FUNCTION, \

         NAME, FALSE, 0, 0, IN)

@end example

@strong{Description}@*

This is used to fill in an empty howto entry in an array.

@example

#define EMPTY_HOWTO(C) \

  HOWTO ((C), 0, 0, 0, FALSE, 0, complain_overflow_dont, NULL, \

         NULL, FALSE, 0, 0, FALSE)

@end example

@strong{Description}@*

Helper routine to turn a symbol into a relocation value.

@example

#define HOWTO_PREPARE(relocation, symbol)               \

  @{                                                     \

    if (symbol != NULL)                                 \

      @{                                                 \

        if (bfd_is_com_section (symbol->section))       \

          @{                                             \

            relocation = 0;                             \

          @}                                             \

        else                                            \

          @{                                             \

            relocation = symbol->value;                 \

          @}                                             \

      @}                                                 \

  @}

@end example

@findex bfd_get_reloc_size

@subsubsection @code{bfd_get_reloc_size}

@strong{Synopsis}

@example

unsigned int bfd_get_reloc_size (reloc_howto_type *);

@end example

@strong{Description}@*

For a reloc_howto_type that operates on a fixed number of bytes,

this returns the number of bytes operated on.

@findex arelent_chain

@subsubsection @code{arelent_chain}

@strong{Description}@*

How relocs are tied together in an @code{asection}:

@example

typedef struct relent_chain

@{

  arelent relent;

  struct relent_chain *next;

@}

arelent_chain;

@end example

@findex bfd_check_overflow

@subsubsection @code{bfd_check_overflow}

@strong{Synopsis}

@example

bfd_reloc_status_type bfd_check_overflow

   (enum complain_overflow how,

    unsigned int bitsize,

    unsigned int rightshift,

    unsigned int addrsize,

    bfd_vma relocation);

@end example

@strong{Description}@*

Perform overflow checking on @var{relocation} which has

@var{bitsize} significant bits and will be shifted right by

@var{rightshift} bits, on a machine with addresses containing

@var{addrsize} significant bits.  The result is either of

@code{bfd_reloc_ok} or @code{bfd_reloc_overflow}.

@findex bfd_perform_relocation

@subsubsection @code{bfd_perform_relocation}

@strong{Synopsis}

@example

bfd_reloc_status_type bfd_perform_relocation

   (bfd *abfd,

    arelent *reloc_entry,

    void *data,

    asection *input_section,

    bfd *output_bfd,

    char **error_message);

@end example

@strong{Description}@*

If @var{output_bfd} is supplied to this function, the

generated image will be relocatable; the relocations are

copied to the output file after they have been changed to

reflect the new state of the world. There are two ways of

reflecting the results of partial linkage in an output file:

by modifying the output data in place, and by modifying the

relocation record.  Some native formats (e.g., basic a.out and

basic coff) have no way of specifying an addend in the

relocation type, so the addend has to go in the output data.

This is no big deal since in these formats the output data

slot will always be big enough for the addend. Complex reloc

types with addends were invented to solve just this problem.

The @var{error_message} argument is set to an error message if

this return @code{bfd_reloc_dangerous}.

@findex bfd_install_relocation

@subsubsection @code{bfd_install_relocation}

@strong{Synopsis}

@example

bfd_reloc_status_type bfd_install_relocation

   (bfd *abfd,

    arelent *reloc_entry,

    void *data, bfd_vma data_start,

    asection *input_section,

    char **error_message);

@end example

@strong{Description}@*

This looks remarkably like @code{bfd_perform_relocation}, except it

does not expect that the section contents have been filled in.

I.e., it's suitable for use when creating, rather than applying

a relocation.

For now, this function should be considered reserved for the

assembler.

@node howto manager,  , typedef arelent, Relocations

@subsection The howto manager

When an application wants to create a relocation, but doesn't

know what the target machine might call it, it can find out by

using this bit of code.

@findex bfd_reloc_code_type

@subsubsection @code{bfd_reloc_code_type}

@strong{Description}@*

The insides of a reloc code.  The idea is that, eventually, there

will be one enumerator for every type of relocation we ever do.

Pass one of these values to @code{bfd_reloc_type_lookup}, and it'll

return a howto pointer.

This does mean that the application must determine the correct

enumerator value; you can't get a howto pointer from a random set

of attributes.

Here are the possible values for @code{enum bfd_reloc_code_real}:

@deffn {} BFD_RELOC_64

@deffnx {} BFD_RELOC_32

@deffnx {} BFD_RELOC_26

@deffnx {} BFD_RELOC_24

@deffnx {} BFD_RELOC_16

@deffnx {} BFD_RELOC_14

@deffnx {} BFD_RELOC_8

Basic absolute relocations of N bits.

@end deffn

@deffn {} BFD_RELOC_64_PCREL

@deffnx {} BFD_RELOC_32_PCREL

@deffnx {} BFD_RELOC_24_PCREL

@deffnx {} BFD_RELOC_16_PCREL

@deffnx {} BFD_RELOC_12_PCREL

@deffnx {} BFD_RELOC_8_PCREL

PC-relative relocations.  Sometimes these are relative to the address

of the relocation itself; sometimes they are relative to the start of

the section containing the relocation.  It depends on the specific target.

The 24-bit relocation is used in some Intel 960 configurations.

@end deffn

@deffn {} BFD_RELOC_32_SECREL

Section relative relocations.  Some targets need this for DWARF2.

@end deffn

@deffn {} BFD_RELOC_32_GOT_PCREL

@deffnx {} BFD_RELOC_16_GOT_PCREL

@deffnx {} BFD_RELOC_8_GOT_PCREL

@deffnx {} BFD_RELOC_32_GOTOFF

@deffnx {} BFD_RELOC_16_GOTOFF

@deffnx {} BFD_RELOC_LO16_GOTOFF

@deffnx {} BFD_RELOC_HI16_GOTOFF

@deffnx {} BFD_RELOC_HI16_S_GOTOFF

@deffnx {} BFD_RELOC_8_GOTOFF

@deffnx {} BFD_RELOC_64_PLT_PCREL

@deffnx {} BFD_RELOC_32_PLT_PCREL

@deffnx {} BFD_RELOC_24_PLT_PCREL

@deffnx {} BFD_RELOC_16_PLT_PCREL

@deffnx {} BFD_RELOC_8_PLT_PCREL

@deffnx {} BFD_RELOC_64_PLTOFF

@deffnx {} BFD_RELOC_32_PLTOFF

@deffnx {} BFD_RELOC_16_PLTOFF

@deffnx {} BFD_RELOC_LO16_PLTOFF

@deffnx {} BFD_RELOC_HI16_PLTOFF

@deffnx {} BFD_RELOC_HI16_S_PLTOFF

@deffnx {} BFD_RELOC_8_PLTOFF

For ELF.

@end deffn

@deffn {} BFD_RELOC_68K_GLOB_DAT

@deffnx {} BFD_RELOC_68K_JMP_SLOT

@deffnx {} BFD_RELOC_68K_RELATIVE

@deffnx {} BFD_RELOC_68K_TLS_GD32

@deffnx {} BFD_RELOC_68K_TLS_GD16

@deffnx {} BFD_RELOC_68K_TLS_GD8

@deffnx {} BFD_RELOC_68K_TLS_LDM32

@deffnx {} BFD_RELOC_68K_TLS_LDM16

@deffnx {} BFD_RELOC_68K_TLS_LDM8

@deffnx {} BFD_RELOC_68K_TLS_LDO32

@deffnx {} BFD_RELOC_68K_TLS_LDO16

@deffnx {} BFD_RELOC_68K_TLS_LDO8

@deffnx {} BFD_RELOC_68K_TLS_IE32

@deffnx {} BFD_RELOC_68K_TLS_IE16

@deffnx {} BFD_RELOC_68K_TLS_IE8

@deffnx {} BFD_RELOC_68K_TLS_LE32

@deffnx {} BFD_RELOC_68K_TLS_LE16

@deffnx {} BFD_RELOC_68K_TLS_LE8

Relocations used by 68K ELF.

@end deffn

@deffn {} BFD_RELOC_32_BASEREL

@deffnx {} BFD_RELOC_16_BASEREL

@deffnx {} BFD_RELOC_LO16_BASEREL

@deffnx {} BFD_RELOC_HI16_BASEREL

@deffnx {} BFD_RELOC_HI16_S_BASEREL

@deffnx {} BFD_RELOC_8_BASEREL

@deffnx {} BFD_RELOC_RVA

Linkage-table relative.

@end deffn

@deffn {} BFD_RELOC_8_FFnn

Absolute 8-bit relocation, but used to form an address like 0xFFnn.

@end deffn

@deffn {} BFD_RELOC_32_PCREL_S2

@deffnx {} BFD_RELOC_16_PCREL_S2

@deffnx {} BFD_RELOC_23_PCREL_S2

These PC-relative relocations are stored as word displacements --

i.e., byte displacements shifted right two bits.  The 30-bit word

displacement (<<32_PCREL_S2>> -- 32 bits, shifted 2) is used on the

SPARC.  (SPARC tools generally refer to this as <<WDISP30>>.)  The

signed 16-bit displacement is used on the MIPS, and the 23-bit

displacement is used on the Alpha.

@end deffn

@deffn {} BFD_RELOC_HI22

@deffnx {} BFD_RELOC_LO10

High 22 bits and low 10 bits of 32-bit value, placed into lower bits of

the target word.  These are used on the SPARC.

@end deffn

@deffn {} BFD_RELOC_GPREL16

@deffnx {} BFD_RELOC_GPREL32

For systems that allocate a Global Pointer register, these are

displacements off that register.  These relocation types are

handled specially, because the value the register will have is

decided relatively late.

@end deffn

@deffn {} BFD_RELOC_I960_CALLJ

Reloc types used for i960/b.out.

@end deffn

@deffn {} BFD_RELOC_NONE

@deffnx {} BFD_RELOC_SPARC_WDISP22

@deffnx {} BFD_RELOC_SPARC22

@deffnx {} BFD_RELOC_SPARC13

@deffnx {} BFD_RELOC_SPARC_GOT10

@deffnx {} BFD_RELOC_SPARC_GOT13

@deffnx {} BFD_RELOC_SPARC_GOT22

@deffnx {} BFD_RELOC_SPARC_PC10

@deffnx {} BFD_RELOC_SPARC_PC22

@deffnx {} BFD_RELOC_SPARC_WPLT30

@deffnx {} BFD_RELOC_SPARC_COPY

@deffnx {} BFD_RELOC_SPARC_GLOB_DAT

@deffnx {} BFD_RELOC_SPARC_JMP_SLOT

@deffnx {} BFD_RELOC_SPARC_RELATIVE

@deffnx {} BFD_RELOC_SPARC_UA16

@deffnx {} BFD_RELOC_SPARC_UA32

@deffnx {} BFD_RELOC_SPARC_UA64

@deffnx {} BFD_RELOC_SPARC_GOTDATA_HIX22

@deffnx {} BFD_RELOC_SPARC_GOTDATA_LOX10

@deffnx {} BFD_RELOC_SPARC_GOTDATA_OP_HIX22

@deffnx {} BFD_RELOC_SPARC_GOTDATA_OP_LOX10

@deffnx {} BFD_RELOC_SPARC_GOTDATA_OP

@deffnx {} BFD_RELOC_SPARC_JMP_IREL

@deffnx {} BFD_RELOC_SPARC_IRELATIVE

SPARC ELF relocations.  There is probably some overlap with other

relocation types already defined.

@end deffn

@deffn {} BFD_RELOC_SPARC_BASE13

@deffnx {} BFD_RELOC_SPARC_BASE22

I think these are specific to SPARC a.out (e.g., Sun 4).

@end deffn

@deffn {} BFD_RELOC_SPARC_64

@deffnx {} BFD_RELOC_SPARC_10

@deffnx {} BFD_RELOC_SPARC_11

@deffnx {} BFD_RELOC_SPARC_OLO10

@deffnx {} BFD_RELOC_SPARC_HH22

@deffnx {} BFD_RELOC_SPARC_HM10

@deffnx {} BFD_RELOC_SPARC_LM22

@deffnx {} BFD_RELOC_SPARC_PC_HH22

@deffnx {} BFD_RELOC_SPARC_PC_HM10

@deffnx {} BFD_RELOC_SPARC_PC_LM22

@deffnx {} BFD_RELOC_SPARC_WDISP16

@deffnx {} BFD_RELOC_SPARC_WDISP19

@deffnx {} BFD_RELOC_SPARC_7

@deffnx {} BFD_RELOC_SPARC_6

@deffnx {} BFD_RELOC_SPARC_5

@deffnx {} BFD_RELOC_SPARC_DISP64

@deffnx {} BFD_RELOC_SPARC_PLT32

@deffnx {} BFD_RELOC_SPARC_PLT64

@deffnx {} BFD_RELOC_SPARC_HIX22

@deffnx {} BFD_RELOC_SPARC_LOX10

@deffnx {} BFD_RELOC_SPARC_H44

@deffnx {} BFD_RELOC_SPARC_M44

@deffnx {} BFD_RELOC_SPARC_L44

@deffnx {} BFD_RELOC_SPARC_REGISTER

SPARC64 relocations

@end deffn

@deffn {} BFD_RELOC_SPARC_REV32

SPARC little endian relocation

@end deffn

@deffn {} BFD_RELOC_SPARC_TLS_GD_HI22

@deffnx {} BFD_RELOC_SPARC_TLS_GD_LO10

@deffnx {} BFD_RELOC_SPARC_TLS_GD_ADD

@deffnx {} BFD_RELOC_SPARC_TLS_GD_CALL

@deffnx {} BFD_RELOC_SPARC_TLS_LDM_HI22

@deffnx {} BFD_RELOC_SPARC_TLS_LDM_LO10

@deffnx {} BFD_RELOC_SPARC_TLS_LDM_ADD

@deffnx {} BFD_RELOC_SPARC_TLS_LDM_CALL

@deffnx {} BFD_RELOC_SPARC_TLS_LDO_HIX22

@deffnx {} BFD_RELOC_SPARC_TLS_LDO_LOX10

@deffnx {} BFD_RELOC_SPARC_TLS_LDO_ADD

@deffnx {} BFD_RELOC_SPARC_TLS_IE_HI22

@deffnx {} BFD_RELOC_SPARC_TLS_IE_LO10

@deffnx {} BFD_RELOC_SPARC_TLS_IE_LD

@deffnx {} BFD_RELOC_SPARC_TLS_IE_LDX

@deffnx {} BFD_RELOC_SPARC_TLS_IE_ADD

@deffnx {} BFD_RELOC_SPARC_TLS_LE_HIX22

@deffnx {} BFD_RELOC_SPARC_TLS_LE_LOX10

@deffnx {} BFD_RELOC_SPARC_TLS_DTPMOD32

@deffnx {} BFD_RELOC_SPARC_TLS_DTPMOD64

@deffnx {} BFD_RELOC_SPARC_TLS_DTPOFF32

@deffnx {} BFD_RELOC_SPARC_TLS_DTPOFF64

@deffnx {} BFD_RELOC_SPARC_TLS_TPOFF32

@deffnx {} BFD_RELOC_SPARC_TLS_TPOFF64

SPARC TLS relocations

@end deffn

@deffn {} BFD_RELOC_SPU_IMM7

@deffnx {} BFD_RELOC_SPU_IMM8

@deffnx {} BFD_RELOC_SPU_IMM10

@deffnx {} BFD_RELOC_SPU_IMM10W

@deffnx {} BFD_RELOC_SPU_IMM16

@deffnx {} BFD_RELOC_SPU_IMM16W

@deffnx {} BFD_RELOC_SPU_IMM18

@deffnx {} BFD_RELOC_SPU_PCREL9a

@deffnx {} BFD_RELOC_SPU_PCREL9b

@deffnx {} BFD_RELOC_SPU_PCREL16

@deffnx {} BFD_RELOC_SPU_LO16

@deffnx {} BFD_RELOC_SPU_HI16

@deffnx {} BFD_RELOC_SPU_PPU32

@deffnx {} BFD_RELOC_SPU_PPU64

@deffnx {} BFD_RELOC_SPU_ADD_PIC

SPU Relocations.

@end deffn

@deffn {} BFD_RELOC_ALPHA_GPDISP_HI16

Alpha ECOFF and ELF relocations.  Some of these treat the symbol or

"addend" in some special way.

For GPDISP_HI16 ("gpdisp") relocations, the symbol is ignored when

writing; when reading, it will be the absolute section symbol.  The

addend is the displacement in bytes of the "lda" instruction from

the "ldah" instruction (which is at the address of this reloc).

@end deffn

@deffn {} BFD_RELOC_ALPHA_GPDISP_LO16

For GPDISP_LO16 ("ignore") relocations, the symbol is handled as

with GPDISP_HI16 relocs.  The addend is ignored when writing the

relocations out, and is filled in with the file's GP value on

reading, for convenience.

@end deffn

@deffn {} BFD_RELOC_ALPHA_GPDISP

The ELF GPDISP relocation is exactly the same as the GPDISP_HI16

relocation except that there is no accompanying GPDISP_LO16

relocation.

@end deffn

@deffn {} BFD_RELOC_ALPHA_LITERAL

@deffnx {} BFD_RELOC_ALPHA_ELF_LITERAL

@deffnx {} BFD_RELOC_ALPHA_LITUSE

The Alpha LITERAL/LITUSE relocs are produced by a symbol reference;

the assembler turns it into a LDQ instruction to load the address of

the symbol, and then fills in a register in the real instruction.

The LITERAL reloc, at the LDQ instruction, refers to the .lita

section symbol.  The addend is ignored when writing, but is filled

in with the file's GP value on reading, for convenience, as with the

GPDISP_LO16 reloc.

The ELF_LITERAL reloc is somewhere between 16_GOTOFF and GPDISP_LO16.

It should refer to the symbol to be referenced, as with 16_GOTOFF,

but it generates output not based on the position within the .got

section, but relative to the GP value chosen for the file during the

final link stage.

The LITUSE reloc, on the instruction using the loaded address, gives

information to the linker that it might be able to use to optimize

away some literal section references.  The symbol is ignored (read

as the absolute section symbol), and the "addend" indicates the type

of instruction using the register:

1 - "memory" fmt insn

2 - byte-manipulation (byte offset reg)

3 - jsr (target of branch)

@end deffn

@deffn {} BFD_RELOC_ALPHA_HINT

The HINT relocation indicates a value that should be filled into the

"hint" field of a jmp/jsr/ret instruction, for possible branch-

prediction logic which may be provided on some processors.

@end deffn

@deffn {} BFD_RELOC_ALPHA_LINKAGE

The LINKAGE relocation outputs a linkage pair in the object file,

which is filled by the linker.

@end deffn

@deffn {} BFD_RELOC_ALPHA_CODEADDR

The CODEADDR relocation outputs a STO_CA in the object file,

which is filled by the linker.

@end deffn

@deffn {} BFD_RELOC_ALPHA_GPREL_HI16

@deffnx {} BFD_RELOC_ALPHA_GPREL_LO16

The GPREL_HI/LO relocations together form a 32-bit offset from the

GP register.

@end deffn

@deffn {} BFD_RELOC_ALPHA_BRSGP

Like BFD_RELOC_23_PCREL_S2, except that the source and target must

share a common GP, and the target address is adjusted for

STO_ALPHA_STD_GPLOAD.

@end deffn

@deffn {} BFD_RELOC_ALPHA_NOP

The NOP relocation outputs a NOP if the longword displacement

between two procedure entry points is < 2^21.

@end deffn

@deffn {} BFD_RELOC_ALPHA_BSR

The BSR relocation outputs a BSR if the longword displacement

between two procedure entry points is < 2^21.

@end deffn

@deffn {} BFD_RELOC_ALPHA_LDA

The LDA relocation outputs a LDA if the longword displacement

between two procedure entry points is < 2^16.

@end deffn

@deffn {} BFD_RELOC_ALPHA_BOH

The BOH relocation outputs a BSR if the longword displacement

between two procedure entry points is < 2^21, or else a hint.

@end deffn

@deffn {} BFD_RELOC_ALPHA_TLSGD

@deffnx {} BFD_RELOC_ALPHA_TLSLDM

@deffnx {} BFD_RELOC_ALPHA_DTPMOD64

@deffnx {} BFD_RELOC_ALPHA_GOTDTPREL16

@deffnx {} BFD_RELOC_ALPHA_DTPREL64

@deffnx {} BFD_RELOC_ALPHA_DTPREL_HI16

@deffnx {} BFD_RELOC_ALPHA_DTPREL_LO16

@deffnx {} BFD_RELOC_ALPHA_DTPREL16

@deffnx {} BFD_RELOC_ALPHA_GOTTPREL16

@deffnx {} BFD_RELOC_ALPHA_TPREL64

@deffnx {} BFD_RELOC_ALPHA_TPREL_HI16

@deffnx {} BFD_RELOC_ALPHA_TPREL_LO16

@deffnx {} BFD_RELOC_ALPHA_TPREL16

Alpha thread-local storage relocations.

@end deffn

@deffn {} BFD_RELOC_MIPS_JMP

Bits 27..2 of the relocation address shifted right 2 bits;

simple reloc otherwise.

@end deffn

@deffn {} BFD_RELOC_MIPS16_JMP

The MIPS16 jump instruction.

@end deffn

@deffn {} BFD_RELOC_MIPS16_GPREL

MIPS16 GP relative reloc.

@end deffn

@deffn {} BFD_RELOC_HI16

High 16 bits of 32-bit value; simple reloc.

@end deffn

@deffn {} BFD_RELOC_HI16_S

High 16 bits of 32-bit value but the low 16 bits will be sign

extended and added to form the final result.  If the low 16

bits form a negative number, we need to add one to the high value

to compensate for the borrow when the low bits are added.

@end deffn

@deffn {} BFD_RELOC_LO16

Low 16 bits.

@end deffn

@deffn {} BFD_RELOC_HI16_PCREL

High 16 bits of 32-bit pc-relative value

@end deffn

@deffn {} BFD_RELOC_HI16_S_PCREL

High 16 bits of 32-bit pc-relative value, adjusted

@end deffn

@deffn {} BFD_RELOC_LO16_PCREL

Low 16 bits of pc-relative value

@end deffn

@deffn {} BFD_RELOC_MIPS16_GOT16

@deffnx {} BFD_RELOC_MIPS16_CALL16

Equivalent of BFD_RELOC_MIPS_*, but with the MIPS16 layout of

16-bit immediate fields

@end deffn

@deffn {} BFD_RELOC_MIPS16_HI16

MIPS16 high 16 bits of 32-bit value.

@end deffn

@deffn {} BFD_RELOC_MIPS16_HI16_S

MIPS16 high 16 bits of 32-bit value but the low 16 bits will be sign

extended and added to form the final result.  If the low 16

bits form a negative number, we need to add one to the high value

to compensate for the borrow when the low bits are added.

@end deffn

@deffn {} BFD_RELOC_MIPS16_LO16

MIPS16 low 16 bits.

@end deffn

@deffn {} BFD_RELOC_MIPS_LITERAL

Relocation against a MIPS literal section.

@end deffn

@deffn {} BFD_RELOC_MIPS_GOT16

@deffnx {} BFD_RELOC_MIPS_CALL16

@deffnx {} BFD_RELOC_MIPS_GOT_HI16

@deffnx {} BFD_RELOC_MIPS_GOT_LO16

@deffnx {} BFD_RELOC_MIPS_CALL_HI16

@deffnx {} BFD_RELOC_MIPS_CALL_LO16

@deffnx {} BFD_RELOC_MIPS_SUB

@deffnx {} BFD_RELOC_MIPS_GOT_PAGE

@deffnx {} BFD_RELOC_MIPS_GOT_OFST

@deffnx {} BFD_RELOC_MIPS_GOT_DISP

@deffnx {} BFD_RELOC_MIPS_SHIFT5

@deffnx {} BFD_RELOC_MIPS_SHIFT6

@deffnx {} BFD_RELOC_MIPS_INSERT_A

@deffnx {} BFD_RELOC_MIPS_INSERT_B

@deffnx {} BFD_RELOC_MIPS_DELETE

@deffnx {} BFD_RELOC_MIPS_HIGHEST

@deffnx {} BFD_RELOC_MIPS_HIGHER

@deffnx {} BFD_RELOC_MIPS_SCN_DISP

@deffnx {} BFD_RELOC_MIPS_REL16

@deffnx {} BFD_RELOC_MIPS_RELGOT

@deffnx {} BFD_RELOC_MIPS_JALR

@deffnx {} BFD_RELOC_MIPS_TLS_DTPMOD32

@deffnx {} BFD_RELOC_MIPS_TLS_DTPREL32

@deffnx {} BFD_RELOC_MIPS_TLS_DTPMOD64

@deffnx {} BFD_RELOC_MIPS_TLS_DTPREL64

@deffnx {} BFD_RELOC_MIPS_TLS_GD

@deffnx {} BFD_RELOC_MIPS_TLS_LDM

@deffnx {} BFD_RELOC_MIPS_TLS_DTPREL_HI16

@deffnx {} BFD_RELOC_MIPS_TLS_DTPREL_LO16

@deffnx {} BFD_RELOC_MIPS_TLS_GOTTPREL

@deffnx {} BFD_RELOC_MIPS_TLS_TPREL32

@deffnx {} BFD_RELOC_MIPS_TLS_TPREL64

@deffnx {} BFD_RELOC_MIPS_TLS_TPREL_HI16

@deffnx {} BFD_RELOC_MIPS_TLS_TPREL_LO16

MIPS ELF relocations.

@end deffn

@deffn {} BFD_RELOC_MIPS_COPY

@deffnx {} BFD_RELOC_MIPS_JUMP_SLOT

MIPS ELF relocations (VxWorks and PLT extensions).

@end deffn

@deffn {} BFD_RELOC_MOXIE_10_PCREL

Moxie ELF relocations.

@end deffn

@deffn {} BFD_RELOC_FRV_LABEL16

@deffnx {} BFD_RELOC_FRV_LABEL24

@deffnx {} BFD_RELOC_FRV_LO16

@deffnx {} BFD_RELOC_FRV_HI16

@deffnx {} BFD_RELOC_FRV_GPREL12

@deffnx {} BFD_RELOC_FRV_GPRELU12

@deffnx {} BFD_RELOC_FRV_GPREL32

@deffnx {} BFD_RELOC_FRV_GPRELHI

@deffnx {} BFD_RELOC_FRV_GPRELLO

@deffnx {} BFD_RELOC_FRV_GOT12

@deffnx {} BFD_RELOC_FRV_GOTHI

@deffnx {} BFD_RELOC_FRV_GOTLO

@deffnx {} BFD_RELOC_FRV_FUNCDESC

@deffnx {} BFD_RELOC_FRV_FUNCDESC_GOT12

@deffnx {} BFD_RELOC_FRV_FUNCDESC_GOTHI

@deffnx {} BFD_RELOC_FRV_FUNCDESC_GOTLO

@deffnx {} BFD_RELOC_FRV_FUNCDESC_VALUE

@deffnx {} BFD_RELOC_FRV_FUNCDESC_GOTOFF12

@deffnx {} BFD_RELOC_FRV_FUNCDESC_GOTOFFHI

@deffnx {} BFD_RELOC_FRV_FUNCDESC_GOTOFFLO

@deffnx {} BFD_RELOC_FRV_GOTOFF12

@deffnx {} BFD_RELOC_FRV_GOTOFFHI

@deffnx {} BFD_RELOC_FRV_GOTOFFLO

@deffnx {} BFD_RELOC_FRV_GETTLSOFF

@deffnx {} BFD_RELOC_FRV_TLSDESC_VALUE

@deffnx {} BFD_RELOC_FRV_GOTTLSDESC12

@deffnx {} BFD_RELOC_FRV_GOTTLSDESCHI

@deffnx {} BFD_RELOC_FRV_GOTTLSDESCLO

@deffnx {} BFD_RELOC_FRV_TLSMOFF12

@deffnx {} BFD_RELOC_FRV_TLSMOFFHI

@deffnx {} BFD_RELOC_FRV_TLSMOFFLO

@deffnx {} BFD_RELOC_FRV_GOTTLSOFF12

@deffnx {} BFD_RELOC_FRV_GOTTLSOFFHI