1 /* BFD support for handling relocation entries.
2 Copyright (C) 1990, 91, 92, 93, 94, 95, 96, 97, 98, 99, 2000
3 Free Software Foundation, Inc.
4 Written by Cygnus Support.
6 This file is part of BFD, the Binary File Descriptor library.
8 This program is free software; you can redistribute it and/or modify
9 it under the terms of the GNU General Public License as published by
10 the Free Software Foundation; either version 2 of the License, or
11 (at your option) any later version.
13 This program is distributed in the hope that it will be useful,
14 but WITHOUT ANY WARRANTY; without even the implied warranty of
15 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
16 GNU General Public License for more details.
18 You should have received a copy of the GNU General Public License
19 along with this program; if not, write to the Free Software
20 Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */
26 BFD maintains relocations in much the same way it maintains
27 symbols: they are left alone until required, then read in
28 en-masse and translated into an internal form. A common
29 routine <<bfd_perform_relocation>> acts upon the
30 canonical form to do the fixup.
32 Relocations are maintained on a per section basis,
33 while symbols are maintained on a per BFD basis.
35 All that a back end has to do to fit the BFD interface is to create
36 a <<struct reloc_cache_entry>> for each relocation
37 in a particular section, and fill in the right bits of the structures.
46 /* DO compile in the reloc_code name table from libbfd.h. */
47 #define _BFD_MAKE_TABLE_bfd_reloc_code_real
56 typedef arelent, howto manager, Relocations, Relocations
61 This is the structure of a relocation entry:
65 .typedef enum bfd_reloc_status
67 . {* No errors detected *}
70 . {* The relocation was performed, but there was an overflow. *}
73 . {* The address to relocate was not within the section supplied. *}
74 . bfd_reloc_outofrange,
76 . {* Used by special functions *}
79 . {* Unsupported relocation size requested. *}
80 . bfd_reloc_notsupported,
85 . {* The symbol to relocate against was undefined. *}
86 . bfd_reloc_undefined,
88 . {* The relocation was performed, but may not be ok - presently
89 . generated only when linking i960 coff files with i960 b.out
90 . symbols. If this type is returned, the error_message argument
91 . to bfd_perform_relocation will be set. *}
94 . bfd_reloc_status_type;
97 .typedef struct reloc_cache_entry
99 . {* A pointer into the canonical table of pointers *}
100 . struct symbol_cache_entry **sym_ptr_ptr;
102 . {* offset in section *}
103 . bfd_size_type address;
105 . {* addend for relocation value *}
108 . {* Pointer to how to perform the required relocation *}
109 . reloc_howto_type *howto;
118 Here is a description of each of the fields within an <<arelent>>:
122 The symbol table pointer points to a pointer to the symbol
123 associated with the relocation request. It is
124 the pointer into the table returned by the back end's
125 <<get_symtab>> action. @xref{Symbols}. The symbol is referenced
126 through a pointer to a pointer so that tools like the linker
127 can fix up all the symbols of the same name by modifying only
128 one pointer. The relocation routine looks in the symbol and
129 uses the base of the section the symbol is attached to and the
130 value of the symbol as the initial relocation offset. If the
131 symbol pointer is zero, then the section provided is looked up.
135 The <<address>> field gives the offset in bytes from the base of
136 the section data which owns the relocation record to the first
137 byte of relocatable information. The actual data relocated
138 will be relative to this point; for example, a relocation
139 type which modifies the bottom two bytes of a four byte word
140 would not touch the first byte pointed to in a big endian
145 The <<addend>> is a value provided by the back end to be added (!)
146 to the relocation offset. Its interpretation is dependent upon
147 the howto. For example, on the 68k the code:
152 | return foo[0x12345678];
155 Could be compiled into:
158 | moveb @@#12345678,d0
163 This could create a reloc pointing to <<foo>>, but leave the
164 offset in the data, something like:
166 |RELOCATION RECORDS FOR [.text]:
170 |00000000 4e56 fffc ; linkw fp,#-4
171 |00000004 1039 1234 5678 ; moveb @@#12345678,d0
172 |0000000a 49c0 ; extbl d0
173 |0000000c 4e5e ; unlk fp
176 Using coff and an 88k, some instructions don't have enough
177 space in them to represent the full address range, and
178 pointers have to be loaded in two parts. So you'd get something like:
180 | or.u r13,r0,hi16(_foo+0x12345678)
181 | ld.b r2,r13,lo16(_foo+0x12345678)
184 This should create two relocs, both pointing to <<_foo>>, and with
185 0x12340000 in their addend field. The data would consist of:
187 |RELOCATION RECORDS FOR [.text]:
189 |00000002 HVRT16 _foo+0x12340000
190 |00000006 LVRT16 _foo+0x12340000
192 |00000000 5da05678 ; or.u r13,r0,0x5678
193 |00000004 1c4d5678 ; ld.b r2,r13,0x5678
194 |00000008 f400c001 ; jmp r1
196 The relocation routine digs out the value from the data, adds
197 it to the addend to get the original offset, and then adds the
198 value of <<_foo>>. Note that all 32 bits have to be kept around
199 somewhere, to cope with carry from bit 15 to bit 16.
201 One further example is the sparc and the a.out format. The
202 sparc has a similar problem to the 88k, in that some
203 instructions don't have room for an entire offset, but on the
204 sparc the parts are created in odd sized lumps. The designers of
205 the a.out format chose to not use the data within the section
206 for storing part of the offset; all the offset is kept within
207 the reloc. Anything in the data should be ignored.
210 | sethi %hi(_foo+0x12345678),%g2
211 | ldsb [%g2+%lo(_foo+0x12345678)],%i0
215 Both relocs contain a pointer to <<foo>>, and the offsets
218 |RELOCATION RECORDS FOR [.text]:
220 |00000004 HI22 _foo+0x12345678
221 |00000008 LO10 _foo+0x12345678
223 |00000000 9de3bf90 ; save %sp,-112,%sp
224 |00000004 05000000 ; sethi %hi(_foo+0),%g2
225 |00000008 f048a000 ; ldsb [%g2+%lo(_foo+0)],%i0
226 |0000000c 81c7e008 ; ret
227 |00000010 81e80000 ; restore
231 The <<howto>> field can be imagined as a
232 relocation instruction. It is a pointer to a structure which
233 contains information on what to do with all of the other
234 information in the reloc record and data section. A back end
235 would normally have a relocation instruction set and turn
236 relocations into pointers to the correct structure on input -
237 but it would be possible to create each howto field on demand.
243 <<enum complain_overflow>>
245 Indicates what sort of overflow checking should be done when
246 performing a relocation.
250 .enum complain_overflow
252 . {* Do not complain on overflow. *}
253 . complain_overflow_dont,
255 . {* Complain if the bitfield overflows, whether it is considered
256 . as signed or unsigned. *}
257 . complain_overflow_bitfield,
259 . {* Complain if the value overflows when considered as signed
261 . complain_overflow_signed,
263 . {* Complain if the value overflows when considered as an
264 . unsigned number. *}
265 . complain_overflow_unsigned
274 The <<reloc_howto_type>> is a structure which contains all the
275 information that libbfd needs to know to tie up a back end's data.
278 .struct symbol_cache_entry; {* Forward declaration *}
280 .struct reloc_howto_struct
282 . {* The type field has mainly a documentary use - the back end can
283 . do what it wants with it, though normally the back end's
284 . external idea of what a reloc number is stored
285 . in this field. For example, a PC relative word relocation
286 . in a coff environment has the type 023 - because that's
287 . what the outside world calls a R_PCRWORD reloc. *}
290 . {* The value the final relocation is shifted right by. This drops
291 . unwanted data from the relocation. *}
292 . unsigned int rightshift;
294 . {* The size of the item to be relocated. This is *not* a
295 . power-of-two measure. To get the number of bytes operated
296 . on by a type of relocation, use bfd_get_reloc_size. *}
299 . {* The number of bits in the item to be relocated. This is used
300 . when doing overflow checking. *}
301 . unsigned int bitsize;
303 . {* Notes that the relocation is relative to the location in the
304 . data section of the addend. The relocation function will
305 . subtract from the relocation value the address of the location
306 . being relocated. *}
307 . boolean pc_relative;
309 . {* The bit position of the reloc value in the destination.
310 . The relocated value is left shifted by this amount. *}
311 . unsigned int bitpos;
313 . {* What type of overflow error should be checked for when
315 . enum complain_overflow complain_on_overflow;
317 . {* If this field is non null, then the supplied function is
318 . called rather than the normal function. This allows really
319 . strange relocation methods to be accomodated (e.g., i960 callj
321 . bfd_reloc_status_type (*special_function)
322 . PARAMS ((bfd *abfd,
323 . arelent *reloc_entry,
324 . struct symbol_cache_entry *symbol,
326 . asection *input_section,
328 . char **error_message));
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
335 . distinction between USE_REL and USE_RELA (though the code checks
336 . for USE_REL == 1/0). The value of this field is TRUE if the
337 . addend is recorded with the section contents; when performing a
338 . partial link (ld -r) the section contents (the data) will be
339 . modified. The value of this field is FALSE if addends are
340 . recorded with the relocation (in arelent.addend); when performing
341 . a partial link the relocation will be modified.
342 . All relocations for all ELF USE_RELA targets should set this field
343 . to FALSE (values of TRUE should be looked on with suspicion).
344 . However, the converse is not true: not all relocations of all ELF
345 . USE_REL targets set this field to TRUE. Why this is so is peculiar
346 . to each particular target. For relocs that aren't used in partial
347 . links (e.g. GOT stuff) it doesn't matter what this is set to. *}
348 . boolean partial_inplace;
350 . {* The src_mask selects which parts of the read in data
351 . are to be used in the relocation sum. E.g., if this was an 8 bit
352 . byte of data which we read and relocated, this would be
353 . 0x000000ff. When we have relocs which have an addend, such as
354 . sun4 extended relocs, the value in the offset part of a
355 . relocating field is garbage so we never use it. In this case
356 . the mask would be 0x00000000. *}
359 . {* The dst_mask selects which parts of the instruction are replaced
360 . into the instruction. In most cases src_mask == dst_mask,
361 . except in the above special case, where dst_mask would be
362 . 0x000000ff, and src_mask would be 0x00000000. *}
365 . {* When some formats create PC relative instructions, they leave
366 . the value of the pc of the place being relocated in the offset
367 . slot of the instruction, so that a PC relative relocation can
368 . be made just by adding in an ordinary offset (e.g., sun3 a.out).
369 . Some formats leave the displacement part of an instruction
370 . empty (e.g., m88k bcs); this flag signals the fact.*}
371 . boolean pcrel_offset;
382 The HOWTO define is horrible and will go away.
384 .#define HOWTO(C, R,S,B, P, BI, O, SF, NAME, INPLACE, MASKSRC, MASKDST, PC) \
385 . {(unsigned)C,R,S,B, P, BI, O,SF,NAME,INPLACE,MASKSRC,MASKDST,PC}
388 And will be replaced with the totally magic way. But for the
389 moment, we are compatible, so do it this way.
391 .#define NEWHOWTO( FUNCTION, NAME,SIZE,REL,IN) HOWTO(0,0,SIZE,0,REL,0,complain_overflow_dont,FUNCTION, NAME,false,0,0,IN)
395 This is used to fill in an empty howto entry in an array.
397 .#define EMPTY_HOWTO(C) \
398 . HOWTO((C),0,0,0,false,0,complain_overflow_dont,NULL,NULL,false,0,0,false)
402 Helper routine to turn a symbol into a relocation value.
404 .#define HOWTO_PREPARE(relocation, symbol) \
406 . if (symbol != (asymbol *)NULL) { \
407 . if (bfd_is_com_section (symbol->section)) { \
411 . relocation = symbol->value; \
423 unsigned int bfd_get_reloc_size (reloc_howto_type *);
426 For a reloc_howto_type that operates on a fixed number of bytes,
427 this returns the number of bytes operated on.
431 bfd_get_reloc_size (howto
)
432 reloc_howto_type
*howto
;
453 How relocs are tied together in an <<asection>>:
455 .typedef struct relent_chain {
457 . struct relent_chain *next;
462 /* N_ONES produces N one bits, without overflowing machine arithmetic. */
463 #define N_ONES(n) (((((bfd_vma) 1 << ((n) - 1)) - 1) << 1) | 1)
470 bfd_reloc_status_type
472 (enum complain_overflow how,
473 unsigned int bitsize,
474 unsigned int rightshift,
475 unsigned int addrsize,
479 Perform overflow checking on @var{relocation} which has
480 @var{bitsize} significant bits and will be shifted right by
481 @var{rightshift} bits, on a machine with addresses containing
482 @var{addrsize} significant bits. The result is either of
483 @code{bfd_reloc_ok} or @code{bfd_reloc_overflow}.
487 bfd_reloc_status_type
488 bfd_check_overflow (how
, bitsize
, rightshift
, addrsize
, relocation
)
489 enum complain_overflow how
;
490 unsigned int bitsize
;
491 unsigned int rightshift
;
492 unsigned int addrsize
;
495 bfd_vma fieldmask
, addrmask
, signmask
, ss
, a
;
496 bfd_reloc_status_type flag
= bfd_reloc_ok
;
500 /* Note: BITSIZE should always be <= ADDRSIZE, but in case it's not,
501 we'll be permissive: extra bits in the field mask will
502 automatically extend the address mask for purposes of the
504 fieldmask
= N_ONES (bitsize
);
505 addrmask
= N_ONES (addrsize
) | fieldmask
;
509 case complain_overflow_dont
:
512 case complain_overflow_signed
:
513 /* If any sign bits are set, all sign bits must be set. That
514 is, A must be a valid negative address after shifting. */
515 a
= (a
& addrmask
) >> rightshift
;
516 signmask
= ~ (fieldmask
>> 1);
518 if (ss
!= 0 && ss
!= ((addrmask
>> rightshift
) & signmask
))
519 flag
= bfd_reloc_overflow
;
522 case complain_overflow_unsigned
:
523 /* We have an overflow if the address does not fit in the field. */
524 a
= (a
& addrmask
) >> rightshift
;
525 if ((a
& ~ fieldmask
) != 0)
526 flag
= bfd_reloc_overflow
;
529 case complain_overflow_bitfield
:
530 /* Bitfields are sometimes signed, sometimes unsigned. We
531 explicitly allow an address wrap too, which means a bitfield
532 of n bits is allowed to store -2**n to 2**n-1. Thus overflow
533 if the value has some, but not all, bits set outside the
536 ss
= a
& ~ fieldmask
;
537 if (ss
!= 0 && ss
!= (((bfd_vma
) -1 >> rightshift
) & ~ fieldmask
))
538 flag
= bfd_reloc_overflow
;
550 bfd_perform_relocation
553 bfd_reloc_status_type
554 bfd_perform_relocation
556 arelent *reloc_entry,
558 asection *input_section,
560 char **error_message);
563 If @var{output_bfd} is supplied to this function, the
564 generated image will be relocatable; the relocations are
565 copied to the output file after they have been changed to
566 reflect the new state of the world. There are two ways of
567 reflecting the results of partial linkage in an output file:
568 by modifying the output data in place, and by modifying the
569 relocation record. Some native formats (e.g., basic a.out and
570 basic coff) have no way of specifying an addend in the
571 relocation type, so the addend has to go in the output data.
572 This is no big deal since in these formats the output data
573 slot will always be big enough for the addend. Complex reloc
574 types with addends were invented to solve just this problem.
575 The @var{error_message} argument is set to an error message if
576 this return @code{bfd_reloc_dangerous}.
580 bfd_reloc_status_type
581 bfd_perform_relocation (abfd
, reloc_entry
, data
, input_section
, output_bfd
,
584 arelent
*reloc_entry
;
586 asection
*input_section
;
588 char **error_message
;
591 bfd_reloc_status_type flag
= bfd_reloc_ok
;
592 bfd_size_type octets
= reloc_entry
->address
* bfd_octets_per_byte (abfd
);
593 bfd_vma output_base
= 0;
594 reloc_howto_type
*howto
= reloc_entry
->howto
;
595 asection
*reloc_target_output_section
;
598 symbol
= *(reloc_entry
->sym_ptr_ptr
);
599 if (bfd_is_abs_section (symbol
->section
)
600 && output_bfd
!= (bfd
*) NULL
)
602 reloc_entry
->address
+= input_section
->output_offset
;
606 /* If we are not producing relocateable output, return an error if
607 the symbol is not defined. An undefined weak symbol is
608 considered to have a value of zero (SVR4 ABI, p. 4-27). */
609 if (bfd_is_und_section (symbol
->section
)
610 && (symbol
->flags
& BSF_WEAK
) == 0
611 && output_bfd
== (bfd
*) NULL
)
612 flag
= bfd_reloc_undefined
;
614 /* If there is a function supplied to handle this relocation type,
615 call it. It'll return `bfd_reloc_continue' if further processing
617 if (howto
->special_function
)
619 bfd_reloc_status_type cont
;
620 cont
= howto
->special_function (abfd
, reloc_entry
, symbol
, data
,
621 input_section
, output_bfd
,
623 if (cont
!= bfd_reloc_continue
)
627 /* Is the address of the relocation really within the section? */
628 if (reloc_entry
->address
> input_section
->_cooked_size
/
629 bfd_octets_per_byte (abfd
))
630 return bfd_reloc_outofrange
;
632 /* Work out which section the relocation is targetted at and the
633 initial relocation command value. */
635 /* Get symbol value. (Common symbols are special.) */
636 if (bfd_is_com_section (symbol
->section
))
639 relocation
= symbol
->value
;
641 reloc_target_output_section
= symbol
->section
->output_section
;
643 /* Convert input-section-relative symbol value to absolute. */
644 if (output_bfd
&& howto
->partial_inplace
== false)
647 output_base
= reloc_target_output_section
->vma
;
649 relocation
+= output_base
+ symbol
->section
->output_offset
;
651 /* Add in supplied addend. */
652 relocation
+= reloc_entry
->addend
;
654 /* Here the variable relocation holds the final address of the
655 symbol we are relocating against, plus any addend. */
657 if (howto
->pc_relative
== true)
659 /* This is a PC relative relocation. We want to set RELOCATION
660 to the distance between the address of the symbol and the
661 location. RELOCATION is already the address of the symbol.
663 We start by subtracting the address of the section containing
666 If pcrel_offset is set, we must further subtract the position
667 of the location within the section. Some targets arrange for
668 the addend to be the negative of the position of the location
669 within the section; for example, i386-aout does this. For
670 i386-aout, pcrel_offset is false. Some other targets do not
671 include the position of the location; for example, m88kbcs,
672 or ELF. For those targets, pcrel_offset is true.
674 If we are producing relocateable output, then we must ensure
675 that this reloc will be correctly computed when the final
676 relocation is done. If pcrel_offset is false we want to wind
677 up with the negative of the location within the section,
678 which means we must adjust the existing addend by the change
679 in the location within the section. If pcrel_offset is true
680 we do not want to adjust the existing addend at all.
682 FIXME: This seems logical to me, but for the case of
683 producing relocateable output it is not what the code
684 actually does. I don't want to change it, because it seems
685 far too likely that something will break. */
688 input_section
->output_section
->vma
+ input_section
->output_offset
;
690 if (howto
->pcrel_offset
== true)
691 relocation
-= reloc_entry
->address
;
694 if (output_bfd
!= (bfd
*) NULL
)
696 if (howto
->partial_inplace
== false)
698 /* This is a partial relocation, and we want to apply the relocation
699 to the reloc entry rather than the raw data. Modify the reloc
700 inplace to reflect what we now know. */
701 reloc_entry
->addend
= relocation
;
702 reloc_entry
->address
+= input_section
->output_offset
;
707 /* This is a partial relocation, but inplace, so modify the
710 If we've relocated with a symbol with a section, change
711 into a ref to the section belonging to the symbol. */
713 reloc_entry
->address
+= input_section
->output_offset
;
716 if (abfd
->xvec
->flavour
== bfd_target_coff_flavour
717 && strcmp (abfd
->xvec
->name
, "coff-Intel-little") != 0
718 && strcmp (abfd
->xvec
->name
, "coff-Intel-big") != 0)
721 /* For m68k-coff, the addend was being subtracted twice during
722 relocation with -r. Removing the line below this comment
723 fixes that problem; see PR 2953.
725 However, Ian wrote the following, regarding removing the line below,
726 which explains why it is still enabled: --djm
728 If you put a patch like that into BFD you need to check all the COFF
729 linkers. I am fairly certain that patch will break coff-i386 (e.g.,
730 SCO); see coff_i386_reloc in coff-i386.c where I worked around the
731 problem in a different way. There may very well be a reason that the
732 code works as it does.
734 Hmmm. The first obvious point is that bfd_perform_relocation should
735 not have any tests that depend upon the flavour. It's seem like
736 entirely the wrong place for such a thing. The second obvious point
737 is that the current code ignores the reloc addend when producing
738 relocateable output for COFF. That's peculiar. In fact, I really
739 have no idea what the point of the line you want to remove is.
741 A typical COFF reloc subtracts the old value of the symbol and adds in
742 the new value to the location in the object file (if it's a pc
743 relative reloc it adds the difference between the symbol value and the
744 location). When relocating we need to preserve that property.
746 BFD handles this by setting the addend to the negative of the old
747 value of the symbol. Unfortunately it handles common symbols in a
748 non-standard way (it doesn't subtract the old value) but that's a
749 different story (we can't change it without losing backward
750 compatibility with old object files) (coff-i386 does subtract the old
751 value, to be compatible with existing coff-i386 targets, like SCO).
753 So everything works fine when not producing relocateable output. When
754 we are producing relocateable output, logically we should do exactly
755 what we do when not producing relocateable output. Therefore, your
756 patch is correct. In fact, it should probably always just set
757 reloc_entry->addend to 0 for all cases, since it is, in fact, going to
758 add the value into the object file. This won't hurt the COFF code,
759 which doesn't use the addend; I'm not sure what it will do to other
760 formats (the thing to check for would be whether any formats both use
761 the addend and set partial_inplace).
763 When I wanted to make coff-i386 produce relocateable output, I ran
764 into the problem that you are running into: I wanted to remove that
765 line. Rather than risk it, I made the coff-i386 relocs use a special
766 function; it's coff_i386_reloc in coff-i386.c. The function
767 specifically adds the addend field into the object file, knowing that
768 bfd_perform_relocation is not going to. If you remove that line, then
769 coff-i386.c will wind up adding the addend field in twice. It's
770 trivial to fix; it just needs to be done.
772 The problem with removing the line is just that it may break some
773 working code. With BFD it's hard to be sure of anything. The right
774 way to deal with this is simply to build and test at least all the
775 supported COFF targets. It should be straightforward if time and disk
776 space consuming. For each target:
778 2) generate some executable, and link it using -r (I would
779 probably use paranoia.o and link against newlib/libc.a, which
780 for all the supported targets would be available in
781 /usr/cygnus/progressive/H-host/target/lib/libc.a).
782 3) make the change to reloc.c
783 4) rebuild the linker
785 6) if the resulting object files are the same, you have at least
787 7) if they are different you have to figure out which version is
790 relocation
-= reloc_entry
->addend
;
792 reloc_entry
->addend
= 0;
796 reloc_entry
->addend
= relocation
;
802 reloc_entry
->addend
= 0;
805 /* FIXME: This overflow checking is incomplete, because the value
806 might have overflowed before we get here. For a correct check we
807 need to compute the value in a size larger than bitsize, but we
808 can't reasonably do that for a reloc the same size as a host
810 FIXME: We should also do overflow checking on the result after
811 adding in the value contained in the object file. */
812 if (howto
->complain_on_overflow
!= complain_overflow_dont
813 && flag
== bfd_reloc_ok
)
814 flag
= bfd_check_overflow (howto
->complain_on_overflow
,
817 bfd_arch_bits_per_address (abfd
),
821 Either we are relocating all the way, or we don't want to apply
822 the relocation to the reloc entry (probably because there isn't
823 any room in the output format to describe addends to relocs)
826 /* The cast to bfd_vma avoids a bug in the Alpha OSF/1 C compiler
827 (OSF version 1.3, compiler version 3.11). It miscompiles the
841 x <<= (unsigned long) s.i0;
845 printf ("succeeded (%lx)\n", x);
849 relocation
>>= (bfd_vma
) howto
->rightshift
;
851 /* Shift everything up to where it's going to be used */
853 relocation
<<= (bfd_vma
) howto
->bitpos
;
855 /* Wait for the day when all have the mask in them */
858 i instruction to be left alone
859 o offset within instruction
860 r relocation offset to apply
869 (( i i i i i o o o o o from bfd_get<size>
870 and S S S S S) to get the size offset we want
871 + r r r r r r r r r r) to get the final value to place
872 and D D D D D to chop to right size
873 -----------------------
876 ( i i i i i o o o o o from bfd_get<size>
877 and N N N N N ) get instruction
878 -----------------------
884 -----------------------
885 = R R R R R R R R R R put into bfd_put<size>
889 x = ( (x & ~howto->dst_mask) | (((x & howto->src_mask) + relocation) & howto->dst_mask))
895 char x
= bfd_get_8 (abfd
, (char *) data
+ octets
);
897 bfd_put_8 (abfd
, x
, (unsigned char *) data
+ octets
);
903 short x
= bfd_get_16 (abfd
, (bfd_byte
*) data
+ octets
);
905 bfd_put_16 (abfd
, x
, (unsigned char *) data
+ octets
);
910 long x
= bfd_get_32 (abfd
, (bfd_byte
*) data
+ octets
);
912 bfd_put_32 (abfd
, x
, (bfd_byte
*) data
+ octets
);
917 long x
= bfd_get_32 (abfd
, (bfd_byte
*) data
+ octets
);
918 relocation
= -relocation
;
920 bfd_put_32 (abfd
, x
, (bfd_byte
*) data
+ octets
);
926 long x
= bfd_get_16 (abfd
, (bfd_byte
*) data
+ octets
);
927 relocation
= -relocation
;
929 bfd_put_16 (abfd
, x
, (bfd_byte
*) data
+ octets
);
940 bfd_vma x
= bfd_get_64 (abfd
, (bfd_byte
*) data
+ octets
);
942 bfd_put_64 (abfd
, x
, (bfd_byte
*) data
+ octets
);
949 return bfd_reloc_other
;
957 bfd_install_relocation
960 bfd_reloc_status_type
961 bfd_install_relocation
963 arelent *reloc_entry,
964 PTR data, bfd_vma data_start,
965 asection *input_section,
966 char **error_message);
969 This looks remarkably like <<bfd_perform_relocation>>, except it
970 does not expect that the section contents have been filled in.
971 I.e., it's suitable for use when creating, rather than applying
974 For now, this function should be considered reserved for the
979 bfd_reloc_status_type
980 bfd_install_relocation (abfd
, reloc_entry
, data_start
, data_start_offset
,
981 input_section
, error_message
)
983 arelent
*reloc_entry
;
985 bfd_vma data_start_offset
;
986 asection
*input_section
;
987 char **error_message
;
990 bfd_reloc_status_type flag
= bfd_reloc_ok
;
991 bfd_size_type octets
= reloc_entry
->address
* bfd_octets_per_byte (abfd
);
992 bfd_vma output_base
= 0;
993 reloc_howto_type
*howto
= reloc_entry
->howto
;
994 asection
*reloc_target_output_section
;
998 symbol
= *(reloc_entry
->sym_ptr_ptr
);
999 if (bfd_is_abs_section (symbol
->section
))
1001 reloc_entry
->address
+= input_section
->output_offset
;
1002 return bfd_reloc_ok
;
1005 /* If there is a function supplied to handle this relocation type,
1006 call it. It'll return `bfd_reloc_continue' if further processing
1008 if (howto
->special_function
)
1010 bfd_reloc_status_type cont
;
1012 /* XXX - The special_function calls haven't been fixed up to deal
1013 with creating new relocations and section contents. */
1014 cont
= howto
->special_function (abfd
, reloc_entry
, symbol
,
1015 /* XXX - Non-portable! */
1016 ((bfd_byte
*) data_start
1017 - data_start_offset
),
1018 input_section
, abfd
, error_message
);
1019 if (cont
!= bfd_reloc_continue
)
1023 /* Is the address of the relocation really within the section? */
1024 if (reloc_entry
->address
> input_section
->_cooked_size
)
1025 return bfd_reloc_outofrange
;
1027 /* Work out which section the relocation is targetted at and the
1028 initial relocation command value. */
1030 /* Get symbol value. (Common symbols are special.) */
1031 if (bfd_is_com_section (symbol
->section
))
1034 relocation
= symbol
->value
;
1036 reloc_target_output_section
= symbol
->section
->output_section
;
1038 /* Convert input-section-relative symbol value to absolute. */
1039 if (howto
->partial_inplace
== false)
1042 output_base
= reloc_target_output_section
->vma
;
1044 relocation
+= output_base
+ symbol
->section
->output_offset
;
1046 /* Add in supplied addend. */
1047 relocation
+= reloc_entry
->addend
;
1049 /* Here the variable relocation holds the final address of the
1050 symbol we are relocating against, plus any addend. */
1052 if (howto
->pc_relative
== true)
1054 /* This is a PC relative relocation. We want to set RELOCATION
1055 to the distance between the address of the symbol and the
1056 location. RELOCATION is already the address of the symbol.
1058 We start by subtracting the address of the section containing
1061 If pcrel_offset is set, we must further subtract the position
1062 of the location within the section. Some targets arrange for
1063 the addend to be the negative of the position of the location
1064 within the section; for example, i386-aout does this. For
1065 i386-aout, pcrel_offset is false. Some other targets do not
1066 include the position of the location; for example, m88kbcs,
1067 or ELF. For those targets, pcrel_offset is true.
1069 If we are producing relocateable output, then we must ensure
1070 that this reloc will be correctly computed when the final
1071 relocation is done. If pcrel_offset is false we want to wind
1072 up with the negative of the location within the section,
1073 which means we must adjust the existing addend by the change
1074 in the location within the section. If pcrel_offset is true
1075 we do not want to adjust the existing addend at all.
1077 FIXME: This seems logical to me, but for the case of
1078 producing relocateable output it is not what the code
1079 actually does. I don't want to change it, because it seems
1080 far too likely that something will break. */
1083 input_section
->output_section
->vma
+ input_section
->output_offset
;
1085 if (howto
->pcrel_offset
== true && howto
->partial_inplace
== true)
1086 relocation
-= reloc_entry
->address
;
1089 if (howto
->partial_inplace
== false)
1091 /* This is a partial relocation, and we want to apply the relocation
1092 to the reloc entry rather than the raw data. Modify the reloc
1093 inplace to reflect what we now know. */
1094 reloc_entry
->addend
= relocation
;
1095 reloc_entry
->address
+= input_section
->output_offset
;
1100 /* This is a partial relocation, but inplace, so modify the
1103 If we've relocated with a symbol with a section, change
1104 into a ref to the section belonging to the symbol. */
1106 reloc_entry
->address
+= input_section
->output_offset
;
1109 if (abfd
->xvec
->flavour
== bfd_target_coff_flavour
1110 && strcmp (abfd
->xvec
->name
, "coff-Intel-little") != 0
1111 && strcmp (abfd
->xvec
->name
, "coff-Intel-big") != 0)
1114 /* For m68k-coff, the addend was being subtracted twice during
1115 relocation with -r. Removing the line below this comment
1116 fixes that problem; see PR 2953.
1118 However, Ian wrote the following, regarding removing the line below,
1119 which explains why it is still enabled: --djm
1121 If you put a patch like that into BFD you need to check all the COFF
1122 linkers. I am fairly certain that patch will break coff-i386 (e.g.,
1123 SCO); see coff_i386_reloc in coff-i386.c where I worked around the
1124 problem in a different way. There may very well be a reason that the
1125 code works as it does.
1127 Hmmm. The first obvious point is that bfd_install_relocation should
1128 not have any tests that depend upon the flavour. It's seem like
1129 entirely the wrong place for such a thing. The second obvious point
1130 is that the current code ignores the reloc addend when producing
1131 relocateable output for COFF. That's peculiar. In fact, I really
1132 have no idea what the point of the line you want to remove is.
1134 A typical COFF reloc subtracts the old value of the symbol and adds in
1135 the new value to the location in the object file (if it's a pc
1136 relative reloc it adds the difference between the symbol value and the
1137 location). When relocating we need to preserve that property.
1139 BFD handles this by setting the addend to the negative of the old
1140 value of the symbol. Unfortunately it handles common symbols in a
1141 non-standard way (it doesn't subtract the old value) but that's a
1142 different story (we can't change it without losing backward
1143 compatibility with old object files) (coff-i386 does subtract the old
1144 value, to be compatible with existing coff-i386 targets, like SCO).
1146 So everything works fine when not producing relocateable output. When
1147 we are producing relocateable output, logically we should do exactly
1148 what we do when not producing relocateable output. Therefore, your
1149 patch is correct. In fact, it should probably always just set
1150 reloc_entry->addend to 0 for all cases, since it is, in fact, going to
1151 add the value into the object file. This won't hurt the COFF code,
1152 which doesn't use the addend; I'm not sure what it will do to other
1153 formats (the thing to check for would be whether any formats both use
1154 the addend and set partial_inplace).
1156 When I wanted to make coff-i386 produce relocateable output, I ran
1157 into the problem that you are running into: I wanted to remove that
1158 line. Rather than risk it, I made the coff-i386 relocs use a special
1159 function; it's coff_i386_reloc in coff-i386.c. The function
1160 specifically adds the addend field into the object file, knowing that
1161 bfd_install_relocation is not going to. If you remove that line, then
1162 coff-i386.c will wind up adding the addend field in twice. It's
1163 trivial to fix; it just needs to be done.
1165 The problem with removing the line is just that it may break some
1166 working code. With BFD it's hard to be sure of anything. The right
1167 way to deal with this is simply to build and test at least all the
1168 supported COFF targets. It should be straightforward if time and disk
1169 space consuming. For each target:
1171 2) generate some executable, and link it using -r (I would
1172 probably use paranoia.o and link against newlib/libc.a, which
1173 for all the supported targets would be available in
1174 /usr/cygnus/progressive/H-host/target/lib/libc.a).
1175 3) make the change to reloc.c
1176 4) rebuild the linker
1178 6) if the resulting object files are the same, you have at least
1180 7) if they are different you have to figure out which version is
1183 relocation
-= reloc_entry
->addend
;
1185 reloc_entry
->addend
= 0;
1189 reloc_entry
->addend
= relocation
;
1193 /* FIXME: This overflow checking is incomplete, because the value
1194 might have overflowed before we get here. For a correct check we
1195 need to compute the value in a size larger than bitsize, but we
1196 can't reasonably do that for a reloc the same size as a host
1198 FIXME: We should also do overflow checking on the result after
1199 adding in the value contained in the object file. */
1200 if (howto
->complain_on_overflow
!= complain_overflow_dont
)
1201 flag
= bfd_check_overflow (howto
->complain_on_overflow
,
1204 bfd_arch_bits_per_address (abfd
),
1208 Either we are relocating all the way, or we don't want to apply
1209 the relocation to the reloc entry (probably because there isn't
1210 any room in the output format to describe addends to relocs)
1213 /* The cast to bfd_vma avoids a bug in the Alpha OSF/1 C compiler
1214 (OSF version 1.3, compiler version 3.11). It miscompiles the
1228 x <<= (unsigned long) s.i0;
1230 printf ("failed\n");
1232 printf ("succeeded (%lx)\n", x);
1236 relocation
>>= (bfd_vma
) howto
->rightshift
;
1238 /* Shift everything up to where it's going to be used */
1240 relocation
<<= (bfd_vma
) howto
->bitpos
;
1242 /* Wait for the day when all have the mask in them */
1245 i instruction to be left alone
1246 o offset within instruction
1247 r relocation offset to apply
1256 (( i i i i i o o o o o from bfd_get<size>
1257 and S S S S S) to get the size offset we want
1258 + r r r r r r r r r r) to get the final value to place
1259 and D D D D D to chop to right size
1260 -----------------------
1263 ( i i i i i o o o o o from bfd_get<size>
1264 and N N N N N ) get instruction
1265 -----------------------
1271 -----------------------
1272 = R R R R R R R R R R put into bfd_put<size>
1276 x = ( (x & ~howto->dst_mask) | (((x & howto->src_mask) + relocation) & howto->dst_mask))
1278 data
= (bfd_byte
*) data_start
+ (octets
- data_start_offset
);
1280 switch (howto
->size
)
1284 char x
= bfd_get_8 (abfd
, (char *) data
);
1286 bfd_put_8 (abfd
, x
, (unsigned char *) data
);
1292 short x
= bfd_get_16 (abfd
, (bfd_byte
*) data
);
1294 bfd_put_16 (abfd
, x
, (unsigned char *) data
);
1299 long x
= bfd_get_32 (abfd
, (bfd_byte
*) data
);
1301 bfd_put_32 (abfd
, x
, (bfd_byte
*) data
);
1306 long x
= bfd_get_32 (abfd
, (bfd_byte
*) data
);
1307 relocation
= -relocation
;
1309 bfd_put_32 (abfd
, x
, (bfd_byte
*) data
);
1319 bfd_vma x
= bfd_get_64 (abfd
, (bfd_byte
*) data
);
1321 bfd_put_64 (abfd
, x
, (bfd_byte
*) data
);
1325 return bfd_reloc_other
;
1331 /* This relocation routine is used by some of the backend linkers.
1332 They do not construct asymbol or arelent structures, so there is no
1333 reason for them to use bfd_perform_relocation. Also,
1334 bfd_perform_relocation is so hacked up it is easier to write a new
1335 function than to try to deal with it.
1337 This routine does a final relocation. Whether it is useful for a
1338 relocateable link depends upon how the object format defines
1341 FIXME: This routine ignores any special_function in the HOWTO,
1342 since the existing special_function values have been written for
1343 bfd_perform_relocation.
1345 HOWTO is the reloc howto information.
1346 INPUT_BFD is the BFD which the reloc applies to.
1347 INPUT_SECTION is the section which the reloc applies to.
1348 CONTENTS is the contents of the section.
1349 ADDRESS is the address of the reloc within INPUT_SECTION.
1350 VALUE is the value of the symbol the reloc refers to.
1351 ADDEND is the addend of the reloc. */
1353 bfd_reloc_status_type
1354 _bfd_final_link_relocate (howto
, input_bfd
, input_section
, contents
, address
,
1356 reloc_howto_type
*howto
;
1358 asection
*input_section
;
1366 /* Sanity check the address. */
1367 if (address
> input_section
->_raw_size
)
1368 return bfd_reloc_outofrange
;
1370 /* This function assumes that we are dealing with a basic relocation
1371 against a symbol. We want to compute the value of the symbol to
1372 relocate to. This is just VALUE, the value of the symbol, plus
1373 ADDEND, any addend associated with the reloc. */
1374 relocation
= value
+ addend
;
1376 /* If the relocation is PC relative, we want to set RELOCATION to
1377 the distance between the symbol (currently in RELOCATION) and the
1378 location we are relocating. Some targets (e.g., i386-aout)
1379 arrange for the contents of the section to be the negative of the
1380 offset of the location within the section; for such targets
1381 pcrel_offset is false. Other targets (e.g., m88kbcs or ELF)
1382 simply leave the contents of the section as zero; for such
1383 targets pcrel_offset is true. If pcrel_offset is false we do not
1384 need to subtract out the offset of the location within the
1385 section (which is just ADDRESS). */
1386 if (howto
->pc_relative
)
1388 relocation
-= (input_section
->output_section
->vma
1389 + input_section
->output_offset
);
1390 if (howto
->pcrel_offset
)
1391 relocation
-= address
;
1394 return _bfd_relocate_contents (howto
, input_bfd
, relocation
,
1395 contents
+ address
);
1398 /* Relocate a given location using a given value and howto. */
1400 bfd_reloc_status_type
1401 _bfd_relocate_contents (howto
, input_bfd
, relocation
, location
)
1402 reloc_howto_type
*howto
;
1409 bfd_reloc_status_type flag
;
1410 unsigned int rightshift
= howto
->rightshift
;
1411 unsigned int bitpos
= howto
->bitpos
;
1413 /* If the size is negative, negate RELOCATION. This isn't very
1415 if (howto
->size
< 0)
1416 relocation
= -relocation
;
1418 /* Get the value we are going to relocate. */
1419 size
= bfd_get_reloc_size (howto
);
1426 x
= bfd_get_8 (input_bfd
, location
);
1429 x
= bfd_get_16 (input_bfd
, location
);
1432 x
= bfd_get_32 (input_bfd
, location
);
1436 x
= bfd_get_64 (input_bfd
, location
);
1443 /* Check for overflow. FIXME: We may drop bits during the addition
1444 which we don't check for. We must either check at every single
1445 operation, which would be tedious, or we must do the computations
1446 in a type larger than bfd_vma, which would be inefficient. */
1447 flag
= bfd_reloc_ok
;
1448 if (howto
->complain_on_overflow
!= complain_overflow_dont
)
1450 bfd_vma addrmask
, fieldmask
, signmask
, ss
;
1453 /* Get the values to be added together. For signed and unsigned
1454 relocations, we assume that all values should be truncated to
1455 the size of an address. For bitfields, all the bits matter.
1456 See also bfd_check_overflow. */
1457 fieldmask
= N_ONES (howto
->bitsize
);
1458 addrmask
= N_ONES (bfd_arch_bits_per_address (input_bfd
)) | fieldmask
;
1460 b
= x
& howto
->src_mask
;
1462 switch (howto
->complain_on_overflow
)
1464 case complain_overflow_signed
:
1465 a
= (a
& addrmask
) >> rightshift
;
1467 /* If any sign bits are set, all sign bits must be set.
1468 That is, A must be a valid negative address after
1470 signmask
= ~ (fieldmask
>> 1);
1472 if (ss
!= 0 && ss
!= ((addrmask
>> rightshift
) & signmask
))
1473 flag
= bfd_reloc_overflow
;
1475 /* We only need this next bit of code if the sign bit of B
1476 is below the sign bit of A. This would only happen if
1477 SRC_MASK had fewer bits than BITSIZE. Note that if
1478 SRC_MASK has more bits than BITSIZE, we can get into
1479 trouble; we would need to verify that B is in range, as
1480 we do for A above. */
1481 signmask
= ((~ howto
->src_mask
) >> 1) & howto
->src_mask
;
1483 /* Set all the bits above the sign bit. */
1484 b
= (b
^ signmask
) - signmask
;
1486 b
= (b
& addrmask
) >> bitpos
;
1488 /* Now we can do the addition. */
1491 /* See if the result has the correct sign. Bits above the
1492 sign bit are junk now; ignore them. If the sum is
1493 positive, make sure we did not have all negative inputs;
1494 if the sum is negative, make sure we did not have all
1495 positive inputs. The test below looks only at the sign
1496 bits, and it really just
1497 SIGN (A) == SIGN (B) && SIGN (A) != SIGN (SUM)
1499 signmask
= (fieldmask
>> 1) + 1;
1500 if (((~ (a
^ b
)) & (a
^ sum
)) & signmask
)
1501 flag
= bfd_reloc_overflow
;
1505 case complain_overflow_unsigned
:
1506 /* Checking for an unsigned overflow is relatively easy:
1507 trim the addresses and add, and trim the result as well.
1508 Overflow is normally indicated when the result does not
1509 fit in the field. However, we also need to consider the
1510 case when, e.g., fieldmask is 0x7fffffff or smaller, an
1511 input is 0x80000000, and bfd_vma is only 32 bits; then we
1512 will get sum == 0, but there is an overflow, since the
1513 inputs did not fit in the field. Instead of doing a
1514 separate test, we can check for this by or-ing in the
1515 operands when testing for the sum overflowing its final
1517 a
= (a
& addrmask
) >> rightshift
;
1518 b
= (b
& addrmask
) >> bitpos
;
1519 sum
= (a
+ b
) & addrmask
;
1520 if ((a
| b
| sum
) & ~ fieldmask
)
1521 flag
= bfd_reloc_overflow
;
1525 case complain_overflow_bitfield
:
1526 /* Much like the signed check, but for a field one bit
1527 wider, and no trimming inputs with addrmask. We allow a
1528 bitfield to represent numbers in the range -2**n to
1529 2**n-1, where n is the number of bits in the field.
1530 Note that when bfd_vma is 32 bits, a 32-bit reloc can't
1531 overflow, which is exactly what we want. */
1534 signmask
= ~ fieldmask
;
1536 if (ss
!= 0 && ss
!= (((bfd_vma
) -1 >> rightshift
) & signmask
))
1537 flag
= bfd_reloc_overflow
;
1539 signmask
= ((~ howto
->src_mask
) >> 1) & howto
->src_mask
;
1540 b
= (b
^ signmask
) - signmask
;
1546 /* We mask with addrmask here to explicitly allow an address
1547 wrap-around. The Linux kernel relies on it, and it is
1548 the only way to write assembler code which can run when
1549 loaded at a location 0x80000000 away from the location at
1550 which it is linked. */
1551 signmask
= fieldmask
+ 1;
1552 if (((~ (a
^ b
)) & (a
^ sum
)) & signmask
& addrmask
)
1553 flag
= bfd_reloc_overflow
;
1562 /* Put RELOCATION in the right bits. */
1563 relocation
>>= (bfd_vma
) rightshift
;
1564 relocation
<<= (bfd_vma
) bitpos
;
1566 /* Add RELOCATION to the right bits of X. */
1567 x
= ((x
& ~howto
->dst_mask
)
1568 | (((x
& howto
->src_mask
) + relocation
) & howto
->dst_mask
));
1570 /* Put the relocated value back in the object file. */
1577 bfd_put_8 (input_bfd
, x
, location
);
1580 bfd_put_16 (input_bfd
, x
, location
);
1583 bfd_put_32 (input_bfd
, x
, location
);
1587 bfd_put_64 (input_bfd
, x
, location
);
1600 howto manager, , typedef arelent, Relocations
1605 When an application wants to create a relocation, but doesn't
1606 know what the target machine might call it, it can find out by
1607 using this bit of code.
1616 The insides of a reloc code. The idea is that, eventually, there
1617 will be one enumerator for every type of relocation we ever do.
1618 Pass one of these values to <<bfd_reloc_type_lookup>>, and it'll
1619 return a howto pointer.
1621 This does mean that the application must determine the correct
1622 enumerator value; you can't get a howto pointer from a random set
1643 Basic absolute relocations of N bits.
1658 PC-relative relocations. Sometimes these are relative to the address
1659 of the relocation itself; sometimes they are relative to the start of
1660 the section containing the relocation. It depends on the specific target.
1662 The 24-bit relocation is used in some Intel 960 configurations.
1665 BFD_RELOC_32_GOT_PCREL
1667 BFD_RELOC_16_GOT_PCREL
1669 BFD_RELOC_8_GOT_PCREL
1675 BFD_RELOC_LO16_GOTOFF
1677 BFD_RELOC_HI16_GOTOFF
1679 BFD_RELOC_HI16_S_GOTOFF
1683 BFD_RELOC_32_PLT_PCREL
1685 BFD_RELOC_24_PLT_PCREL
1687 BFD_RELOC_16_PLT_PCREL
1689 BFD_RELOC_8_PLT_PCREL
1695 BFD_RELOC_LO16_PLTOFF
1697 BFD_RELOC_HI16_PLTOFF
1699 BFD_RELOC_HI16_S_PLTOFF
1706 BFD_RELOC_68K_GLOB_DAT
1708 BFD_RELOC_68K_JMP_SLOT
1710 BFD_RELOC_68K_RELATIVE
1712 Relocations used by 68K ELF.
1715 BFD_RELOC_32_BASEREL
1717 BFD_RELOC_16_BASEREL
1719 BFD_RELOC_LO16_BASEREL
1721 BFD_RELOC_HI16_BASEREL
1723 BFD_RELOC_HI16_S_BASEREL
1729 Linkage-table relative.
1734 Absolute 8-bit relocation, but used to form an address like 0xFFnn.
1737 BFD_RELOC_32_PCREL_S2
1739 BFD_RELOC_16_PCREL_S2
1741 BFD_RELOC_23_PCREL_S2
1743 These PC-relative relocations are stored as word displacements --
1744 i.e., byte displacements shifted right two bits. The 30-bit word
1745 displacement (<<32_PCREL_S2>> -- 32 bits, shifted 2) is used on the
1746 SPARC. (SPARC tools generally refer to this as <<WDISP30>>.) The
1747 signed 16-bit displacement is used on the MIPS, and the 23-bit
1748 displacement is used on the Alpha.
1755 High 22 bits and low 10 bits of 32-bit value, placed into lower bits of
1756 the target word. These are used on the SPARC.
1763 For systems that allocate a Global Pointer register, these are
1764 displacements off that register. These relocation types are
1765 handled specially, because the value the register will have is
1766 decided relatively late.
1769 BFD_RELOC_I960_CALLJ
1771 Reloc types used for i960/b.out.
1776 BFD_RELOC_SPARC_WDISP22
1782 BFD_RELOC_SPARC_GOT10
1784 BFD_RELOC_SPARC_GOT13
1786 BFD_RELOC_SPARC_GOT22
1788 BFD_RELOC_SPARC_PC10
1790 BFD_RELOC_SPARC_PC22
1792 BFD_RELOC_SPARC_WPLT30
1794 BFD_RELOC_SPARC_COPY
1796 BFD_RELOC_SPARC_GLOB_DAT
1798 BFD_RELOC_SPARC_JMP_SLOT
1800 BFD_RELOC_SPARC_RELATIVE
1802 BFD_RELOC_SPARC_UA32
1804 SPARC ELF relocations. There is probably some overlap with other
1805 relocation types already defined.
1808 BFD_RELOC_SPARC_BASE13
1810 BFD_RELOC_SPARC_BASE22
1812 I think these are specific to SPARC a.out (e.g., Sun 4).
1822 BFD_RELOC_SPARC_OLO10
1824 BFD_RELOC_SPARC_HH22
1826 BFD_RELOC_SPARC_HM10
1828 BFD_RELOC_SPARC_LM22
1830 BFD_RELOC_SPARC_PC_HH22
1832 BFD_RELOC_SPARC_PC_HM10
1834 BFD_RELOC_SPARC_PC_LM22
1836 BFD_RELOC_SPARC_WDISP16
1838 BFD_RELOC_SPARC_WDISP19
1846 BFD_RELOC_SPARC_DISP64
1849 BFD_RELOC_SPARC_PLT64
1851 BFD_RELOC_SPARC_HIX22
1853 BFD_RELOC_SPARC_LOX10
1861 BFD_RELOC_SPARC_REGISTER
1866 BFD_RELOC_SPARC_REV32
1868 SPARC little endian relocation
1871 BFD_RELOC_ALPHA_GPDISP_HI16
1873 Alpha ECOFF and ELF relocations. Some of these treat the symbol or
1874 "addend" in some special way.
1875 For GPDISP_HI16 ("gpdisp") relocations, the symbol is ignored when
1876 writing; when reading, it will be the absolute section symbol. The
1877 addend is the displacement in bytes of the "lda" instruction from
1878 the "ldah" instruction (which is at the address of this reloc).
1880 BFD_RELOC_ALPHA_GPDISP_LO16
1882 For GPDISP_LO16 ("ignore") relocations, the symbol is handled as
1883 with GPDISP_HI16 relocs. The addend is ignored when writing the
1884 relocations out, and is filled in with the file's GP value on
1885 reading, for convenience.
1888 BFD_RELOC_ALPHA_GPDISP
1890 The ELF GPDISP relocation is exactly the same as the GPDISP_HI16
1891 relocation except that there is no accompanying GPDISP_LO16
1895 BFD_RELOC_ALPHA_LITERAL
1897 BFD_RELOC_ALPHA_ELF_LITERAL
1899 BFD_RELOC_ALPHA_LITUSE
1901 The Alpha LITERAL/LITUSE relocs are produced by a symbol reference;
1902 the assembler turns it into a LDQ instruction to load the address of
1903 the symbol, and then fills in a register in the real instruction.
1905 The LITERAL reloc, at the LDQ instruction, refers to the .lita
1906 section symbol. The addend is ignored when writing, but is filled
1907 in with the file's GP value on reading, for convenience, as with the
1910 The ELF_LITERAL reloc is somewhere between 16_GOTOFF and GPDISP_LO16.
1911 It should refer to the symbol to be referenced, as with 16_GOTOFF,
1912 but it generates output not based on the position within the .got
1913 section, but relative to the GP value chosen for the file during the
1916 The LITUSE reloc, on the instruction using the loaded address, gives
1917 information to the linker that it might be able to use to optimize
1918 away some literal section references. The symbol is ignored (read
1919 as the absolute section symbol), and the "addend" indicates the type
1920 of instruction using the register:
1921 1 - "memory" fmt insn
1922 2 - byte-manipulation (byte offset reg)
1923 3 - jsr (target of branch)
1925 The GNU linker currently doesn't do any of this optimizing.
1928 BFD_RELOC_ALPHA_USER_LITERAL
1930 BFD_RELOC_ALPHA_USER_LITUSE_BASE
1932 BFD_RELOC_ALPHA_USER_LITUSE_BYTOFF
1934 BFD_RELOC_ALPHA_USER_LITUSE_JSR
1936 BFD_RELOC_ALPHA_USER_GPDISP
1938 BFD_RELOC_ALPHA_USER_GPRELHIGH
1940 BFD_RELOC_ALPHA_USER_GPRELLOW
1942 The BFD_RELOC_ALPHA_USER_* relocations are used by the assembler to
1943 process the explicit !<reloc>!sequence relocations, and are mapped
1944 into the normal relocations at the end of processing.
1947 BFD_RELOC_ALPHA_HINT
1949 The HINT relocation indicates a value that should be filled into the
1950 "hint" field of a jmp/jsr/ret instruction, for possible branch-
1951 prediction logic which may be provided on some processors.
1954 BFD_RELOC_ALPHA_LINKAGE
1956 The LINKAGE relocation outputs a linkage pair in the object file,
1957 which is filled by the linker.
1960 BFD_RELOC_ALPHA_CODEADDR
1962 The CODEADDR relocation outputs a STO_CA in the object file,
1963 which is filled by the linker.
1968 Bits 27..2 of the relocation address shifted right 2 bits;
1969 simple reloc otherwise.
1972 BFD_RELOC_MIPS16_JMP
1974 The MIPS16 jump instruction.
1977 BFD_RELOC_MIPS16_GPREL
1979 MIPS16 GP relative reloc.
1984 High 16 bits of 32-bit value; simple reloc.
1988 High 16 bits of 32-bit value but the low 16 bits will be sign
1989 extended and added to form the final result. If the low 16
1990 bits form a negative number, we need to add one to the high value
1991 to compensate for the borrow when the low bits are added.
1997 BFD_RELOC_PCREL_HI16_S
1999 Like BFD_RELOC_HI16_S, but PC relative.
2001 BFD_RELOC_PCREL_LO16
2003 Like BFD_RELOC_LO16, but PC relative.
2006 BFD_RELOC_MIPS_GPREL
2009 Relocation relative to the global pointer.
2012 BFD_RELOC_MIPS_LITERAL
2014 Relocation against a MIPS literal section.
2017 BFD_RELOC_MIPS_GOT16
2019 BFD_RELOC_MIPS_CALL16
2021 BFD_RELOC_MIPS_GPREL32
2024 BFD_RELOC_MIPS_GOT_HI16
2026 BFD_RELOC_MIPS_GOT_LO16
2028 BFD_RELOC_MIPS_CALL_HI16
2030 BFD_RELOC_MIPS_CALL_LO16
2034 BFD_RELOC_MIPS_GOT_PAGE
2036 BFD_RELOC_MIPS_GOT_OFST
2038 BFD_RELOC_MIPS_GOT_DISP
2041 MIPS ELF relocations.
2052 BFD_RELOC_386_GLOB_DAT
2054 BFD_RELOC_386_JUMP_SLOT
2056 BFD_RELOC_386_RELATIVE
2058 BFD_RELOC_386_GOTOFF
2062 i386/elf relocations
2065 BFD_RELOC_X86_64_GOT32
2067 BFD_RELOC_X86_64_PLT32
2069 BFD_RELOC_X86_64_COPY
2071 BFD_RELOC_X86_64_GLOB_DAT
2073 BFD_RELOC_X86_64_JUMP_SLOT
2075 BFD_RELOC_X86_64_RELATIVE
2077 BFD_RELOC_X86_64_GOTPCREL
2079 BFD_RELOC_X86_64_32S
2081 x86-64/elf relocations
2084 BFD_RELOC_NS32K_IMM_8
2086 BFD_RELOC_NS32K_IMM_16
2088 BFD_RELOC_NS32K_IMM_32
2090 BFD_RELOC_NS32K_IMM_8_PCREL
2092 BFD_RELOC_NS32K_IMM_16_PCREL
2094 BFD_RELOC_NS32K_IMM_32_PCREL
2096 BFD_RELOC_NS32K_DISP_8
2098 BFD_RELOC_NS32K_DISP_16
2100 BFD_RELOC_NS32K_DISP_32
2102 BFD_RELOC_NS32K_DISP_8_PCREL
2104 BFD_RELOC_NS32K_DISP_16_PCREL
2106 BFD_RELOC_NS32K_DISP_32_PCREL
2111 BFD_RELOC_PDP11_DISP_8_PCREL
2113 BFD_RELOC_PDP11_DISP_6_PCREL
2118 BFD_RELOC_PJ_CODE_HI16
2120 BFD_RELOC_PJ_CODE_LO16
2122 BFD_RELOC_PJ_CODE_DIR16
2124 BFD_RELOC_PJ_CODE_DIR32
2126 BFD_RELOC_PJ_CODE_REL16
2128 BFD_RELOC_PJ_CODE_REL32
2130 Picojava relocs. Not all of these appear in object files.
2141 BFD_RELOC_PPC_B16_BRTAKEN
2143 BFD_RELOC_PPC_B16_BRNTAKEN
2147 BFD_RELOC_PPC_BA16_BRTAKEN
2149 BFD_RELOC_PPC_BA16_BRNTAKEN
2153 BFD_RELOC_PPC_GLOB_DAT
2155 BFD_RELOC_PPC_JMP_SLOT
2157 BFD_RELOC_PPC_RELATIVE
2159 BFD_RELOC_PPC_LOCAL24PC
2161 BFD_RELOC_PPC_EMB_NADDR32
2163 BFD_RELOC_PPC_EMB_NADDR16
2165 BFD_RELOC_PPC_EMB_NADDR16_LO
2167 BFD_RELOC_PPC_EMB_NADDR16_HI
2169 BFD_RELOC_PPC_EMB_NADDR16_HA
2171 BFD_RELOC_PPC_EMB_SDAI16
2173 BFD_RELOC_PPC_EMB_SDA2I16
2175 BFD_RELOC_PPC_EMB_SDA2REL
2177 BFD_RELOC_PPC_EMB_SDA21
2179 BFD_RELOC_PPC_EMB_MRKREF
2181 BFD_RELOC_PPC_EMB_RELSEC16
2183 BFD_RELOC_PPC_EMB_RELST_LO
2185 BFD_RELOC_PPC_EMB_RELST_HI
2187 BFD_RELOC_PPC_EMB_RELST_HA
2189 BFD_RELOC_PPC_EMB_BIT_FLD
2191 BFD_RELOC_PPC_EMB_RELSDA
2193 Power(rs6000) and PowerPC relocations.
2198 IBM 370/390 relocations
2203 The type of reloc used to build a contructor table - at the moment
2204 probably a 32 bit wide absolute relocation, but the target can choose.
2205 It generally does map to one of the other relocation types.
2208 BFD_RELOC_ARM_PCREL_BRANCH
2210 ARM 26 bit pc-relative branch. The lowest two bits must be zero and are
2211 not stored in the instruction.
2213 BFD_RELOC_ARM_PCREL_BLX
2215 ARM 26 bit pc-relative branch. The lowest bit must be zero and is
2216 not stored in the instruction. The 2nd lowest bit comes from a 1 bit
2217 field in the instruction.
2219 BFD_RELOC_THUMB_PCREL_BLX
2221 Thumb 22 bit pc-relative branch. The lowest bit must be zero and is
2222 not stored in the instruction. The 2nd lowest bit comes from a 1 bit
2223 field in the instruction.
2225 BFD_RELOC_ARM_IMMEDIATE
2227 BFD_RELOC_ARM_ADRL_IMMEDIATE
2229 BFD_RELOC_ARM_OFFSET_IMM
2231 BFD_RELOC_ARM_SHIFT_IMM
2237 BFD_RELOC_ARM_CP_OFF_IMM
2239 BFD_RELOC_ARM_ADR_IMM
2241 BFD_RELOC_ARM_LDR_IMM
2243 BFD_RELOC_ARM_LITERAL
2245 BFD_RELOC_ARM_IN_POOL
2247 BFD_RELOC_ARM_OFFSET_IMM8
2249 BFD_RELOC_ARM_HWLITERAL
2251 BFD_RELOC_ARM_THUMB_ADD
2253 BFD_RELOC_ARM_THUMB_IMM
2255 BFD_RELOC_ARM_THUMB_SHIFT
2257 BFD_RELOC_ARM_THUMB_OFFSET
2263 BFD_RELOC_ARM_JUMP_SLOT
2267 BFD_RELOC_ARM_GLOB_DAT
2271 BFD_RELOC_ARM_RELATIVE
2273 BFD_RELOC_ARM_GOTOFF
2277 These relocs are only used within the ARM assembler. They are not
2278 (at present) written to any object files.
2281 BFD_RELOC_SH_PCDISP8BY2
2283 BFD_RELOC_SH_PCDISP12BY2
2287 BFD_RELOC_SH_IMM4BY2
2289 BFD_RELOC_SH_IMM4BY4
2293 BFD_RELOC_SH_IMM8BY2
2295 BFD_RELOC_SH_IMM8BY4
2297 BFD_RELOC_SH_PCRELIMM8BY2
2299 BFD_RELOC_SH_PCRELIMM8BY4
2301 BFD_RELOC_SH_SWITCH16
2303 BFD_RELOC_SH_SWITCH32
2317 BFD_RELOC_SH_LOOP_START
2319 BFD_RELOC_SH_LOOP_END
2323 BFD_RELOC_SH_GLOB_DAT
2325 BFD_RELOC_SH_JMP_SLOT
2327 BFD_RELOC_SH_RELATIVE
2331 Hitachi SH relocs. Not all of these appear in object files.
2334 BFD_RELOC_THUMB_PCREL_BRANCH9
2336 BFD_RELOC_THUMB_PCREL_BRANCH12
2338 BFD_RELOC_THUMB_PCREL_BRANCH23
2340 Thumb 23-, 12- and 9-bit pc-relative branches. The lowest bit must
2341 be zero and is not stored in the instruction.
2344 BFD_RELOC_ARC_B22_PCREL
2347 ARC 22 bit pc-relative branch. The lowest two bits must be zero and are
2348 not stored in the instruction. The high 20 bits are installed in bits 26
2349 through 7 of the instruction.
2353 ARC 26 bit absolute branch. The lowest two bits must be zero and are not
2354 stored in the instruction. The high 24 bits are installed in bits 23
2358 BFD_RELOC_D10V_10_PCREL_R
2360 Mitsubishi D10V relocs.
2361 This is a 10-bit reloc with the right 2 bits
2364 BFD_RELOC_D10V_10_PCREL_L
2366 Mitsubishi D10V relocs.
2367 This is a 10-bit reloc with the right 2 bits
2368 assumed to be 0. This is the same as the previous reloc
2369 except it is in the left container, i.e.,
2370 shifted left 15 bits.
2374 This is an 18-bit reloc with the right 2 bits
2377 BFD_RELOC_D10V_18_PCREL
2379 This is an 18-bit reloc with the right 2 bits
2385 Mitsubishi D30V relocs.
2386 This is a 6-bit absolute reloc.
2388 BFD_RELOC_D30V_9_PCREL
2390 This is a 6-bit pc-relative reloc with
2391 the right 3 bits assumed to be 0.
2393 BFD_RELOC_D30V_9_PCREL_R
2395 This is a 6-bit pc-relative reloc with
2396 the right 3 bits assumed to be 0. Same
2397 as the previous reloc but on the right side
2402 This is a 12-bit absolute reloc with the
2403 right 3 bitsassumed to be 0.
2405 BFD_RELOC_D30V_15_PCREL
2407 This is a 12-bit pc-relative reloc with
2408 the right 3 bits assumed to be 0.
2410 BFD_RELOC_D30V_15_PCREL_R
2412 This is a 12-bit pc-relative reloc with
2413 the right 3 bits assumed to be 0. Same
2414 as the previous reloc but on the right side
2419 This is an 18-bit absolute reloc with
2420 the right 3 bits assumed to be 0.
2422 BFD_RELOC_D30V_21_PCREL
2424 This is an 18-bit pc-relative reloc with
2425 the right 3 bits assumed to be 0.
2427 BFD_RELOC_D30V_21_PCREL_R
2429 This is an 18-bit pc-relative reloc with
2430 the right 3 bits assumed to be 0. Same
2431 as the previous reloc but on the right side
2436 This is a 32-bit absolute reloc.
2438 BFD_RELOC_D30V_32_PCREL
2440 This is a 32-bit pc-relative reloc.
2445 Mitsubishi M32R relocs.
2446 This is a 24 bit absolute address.
2448 BFD_RELOC_M32R_10_PCREL
2450 This is a 10-bit pc-relative reloc with the right 2 bits assumed to be 0.
2452 BFD_RELOC_M32R_18_PCREL
2454 This is an 18-bit reloc with the right 2 bits assumed to be 0.
2456 BFD_RELOC_M32R_26_PCREL
2458 This is a 26-bit reloc with the right 2 bits assumed to be 0.
2460 BFD_RELOC_M32R_HI16_ULO
2462 This is a 16-bit reloc containing the high 16 bits of an address
2463 used when the lower 16 bits are treated as unsigned.
2465 BFD_RELOC_M32R_HI16_SLO
2467 This is a 16-bit reloc containing the high 16 bits of an address
2468 used when the lower 16 bits are treated as signed.
2472 This is a 16-bit reloc containing the lower 16 bits of an address.
2474 BFD_RELOC_M32R_SDA16
2476 This is a 16-bit reloc containing the small data area offset for use in
2477 add3, load, and store instructions.
2480 BFD_RELOC_V850_9_PCREL
2482 This is a 9-bit reloc
2484 BFD_RELOC_V850_22_PCREL
2486 This is a 22-bit reloc
2489 BFD_RELOC_V850_SDA_16_16_OFFSET
2491 This is a 16 bit offset from the short data area pointer.
2493 BFD_RELOC_V850_SDA_15_16_OFFSET
2495 This is a 16 bit offset (of which only 15 bits are used) from the
2496 short data area pointer.
2498 BFD_RELOC_V850_ZDA_16_16_OFFSET
2500 This is a 16 bit offset from the zero data area pointer.
2502 BFD_RELOC_V850_ZDA_15_16_OFFSET
2504 This is a 16 bit offset (of which only 15 bits are used) from the
2505 zero data area pointer.
2507 BFD_RELOC_V850_TDA_6_8_OFFSET
2509 This is an 8 bit offset (of which only 6 bits are used) from the
2510 tiny data area pointer.
2512 BFD_RELOC_V850_TDA_7_8_OFFSET
2514 This is an 8bit offset (of which only 7 bits are used) from the tiny
2517 BFD_RELOC_V850_TDA_7_7_OFFSET
2519 This is a 7 bit offset from the tiny data area pointer.
2521 BFD_RELOC_V850_TDA_16_16_OFFSET
2523 This is a 16 bit offset from the tiny data area pointer.
2526 BFD_RELOC_V850_TDA_4_5_OFFSET
2528 This is a 5 bit offset (of which only 4 bits are used) from the tiny
2531 BFD_RELOC_V850_TDA_4_4_OFFSET
2533 This is a 4 bit offset from the tiny data area pointer.
2535 BFD_RELOC_V850_SDA_16_16_SPLIT_OFFSET
2537 This is a 16 bit offset from the short data area pointer, with the
2538 bits placed non-contigously in the instruction.
2540 BFD_RELOC_V850_ZDA_16_16_SPLIT_OFFSET
2542 This is a 16 bit offset from the zero data area pointer, with the
2543 bits placed non-contigously in the instruction.
2545 BFD_RELOC_V850_CALLT_6_7_OFFSET
2547 This is a 6 bit offset from the call table base pointer.
2549 BFD_RELOC_V850_CALLT_16_16_OFFSET
2551 This is a 16 bit offset from the call table base pointer.
2555 BFD_RELOC_MN10300_32_PCREL
2557 This is a 32bit pcrel reloc for the mn10300, offset by two bytes in the
2560 BFD_RELOC_MN10300_16_PCREL
2562 This is a 16bit pcrel reloc for the mn10300, offset by two bytes in the
2568 This is a 8bit DP reloc for the tms320c30, where the most
2569 significant 8 bits of a 24 bit word are placed into the least
2570 significant 8 bits of the opcode.
2573 BFD_RELOC_TIC54X_PARTLS7
2575 This is a 7bit reloc for the tms320c54x, where the least
2576 significant 7 bits of a 16 bit word are placed into the least
2577 significant 7 bits of the opcode.
2580 BFD_RELOC_TIC54X_PARTMS9
2582 This is a 9bit DP reloc for the tms320c54x, where the most
2583 significant 9 bits of a 16 bit word are placed into the least
2584 significant 9 bits of the opcode.
2589 This is an extended address 23-bit reloc for the tms320c54x.
2592 BFD_RELOC_TIC54X_16_OF_23
2594 This is a 16-bit reloc for the tms320c54x, where the least
2595 significant 16 bits of a 23-bit extended address are placed into
2599 BFD_RELOC_TIC54X_MS7_OF_23
2601 This is a reloc for the tms320c54x, where the most
2602 significant 7 bits of a 23-bit extended address are placed into
2608 This is a 48 bit reloc for the FR30 that stores 32 bits.
2612 This is a 32 bit reloc for the FR30 that stores 20 bits split up into
2615 BFD_RELOC_FR30_6_IN_4
2617 This is a 16 bit reloc for the FR30 that stores a 6 bit word offset in
2620 BFD_RELOC_FR30_8_IN_8
2622 This is a 16 bit reloc for the FR30 that stores an 8 bit byte offset
2625 BFD_RELOC_FR30_9_IN_8
2627 This is a 16 bit reloc for the FR30 that stores a 9 bit short offset
2630 BFD_RELOC_FR30_10_IN_8
2632 This is a 16 bit reloc for the FR30 that stores a 10 bit word offset
2635 BFD_RELOC_FR30_9_PCREL
2637 This is a 16 bit reloc for the FR30 that stores a 9 bit pc relative
2638 short offset into 8 bits.
2640 BFD_RELOC_FR30_12_PCREL
2642 This is a 16 bit reloc for the FR30 that stores a 12 bit pc relative
2643 short offset into 11 bits.
2646 BFD_RELOC_MCORE_PCREL_IMM8BY4
2648 BFD_RELOC_MCORE_PCREL_IMM11BY2
2650 BFD_RELOC_MCORE_PCREL_IMM4BY2
2652 BFD_RELOC_MCORE_PCREL_32
2654 BFD_RELOC_MCORE_PCREL_JSR_IMM11BY2
2658 Motorola Mcore relocations.
2661 BFD_RELOC_AVR_7_PCREL
2663 This is a 16 bit reloc for the AVR that stores 8 bit pc relative
2664 short offset into 7 bits.
2666 BFD_RELOC_AVR_13_PCREL
2668 This is a 16 bit reloc for the AVR that stores 13 bit pc relative
2669 short offset into 12 bits.
2673 This is a 16 bit reloc for the AVR that stores 17 bit value (usually
2674 program memory address) into 16 bits.
2676 BFD_RELOC_AVR_LO8_LDI
2678 This is a 16 bit reloc for the AVR that stores 8 bit value (usually
2679 data memory address) into 8 bit immediate value of LDI insn.
2681 BFD_RELOC_AVR_HI8_LDI
2683 This is a 16 bit reloc for the AVR that stores 8 bit value (high 8 bit
2684 of data memory address) into 8 bit immediate value of LDI insn.
2686 BFD_RELOC_AVR_HH8_LDI
2688 This is a 16 bit reloc for the AVR that stores 8 bit value (most high 8 bit
2689 of program memory address) into 8 bit immediate value of LDI insn.
2691 BFD_RELOC_AVR_LO8_LDI_NEG
2693 This is a 16 bit reloc for the AVR that stores negated 8 bit value
2694 (usually data memory address) into 8 bit immediate value of SUBI insn.
2696 BFD_RELOC_AVR_HI8_LDI_NEG
2698 This is a 16 bit reloc for the AVR that stores negated 8 bit value
2699 (high 8 bit of data memory address) into 8 bit immediate value of
2702 BFD_RELOC_AVR_HH8_LDI_NEG
2704 This is a 16 bit reloc for the AVR that stores negated 8 bit value
2705 (most high 8 bit of program memory address) into 8 bit immediate value
2706 of LDI or SUBI insn.
2708 BFD_RELOC_AVR_LO8_LDI_PM
2710 This is a 16 bit reloc for the AVR that stores 8 bit value (usually
2711 command address) into 8 bit immediate value of LDI insn.
2713 BFD_RELOC_AVR_HI8_LDI_PM
2715 This is a 16 bit reloc for the AVR that stores 8 bit value (high 8 bit
2716 of command address) into 8 bit immediate value of LDI insn.
2718 BFD_RELOC_AVR_HH8_LDI_PM
2720 This is a 16 bit reloc for the AVR that stores 8 bit value (most high 8 bit
2721 of command address) into 8 bit immediate value of LDI insn.
2723 BFD_RELOC_AVR_LO8_LDI_PM_NEG
2725 This is a 16 bit reloc for the AVR that stores negated 8 bit value
2726 (usually command address) into 8 bit immediate value of SUBI insn.
2728 BFD_RELOC_AVR_HI8_LDI_PM_NEG
2730 This is a 16 bit reloc for the AVR that stores negated 8 bit value
2731 (high 8 bit of 16 bit command address) into 8 bit immediate value
2734 BFD_RELOC_AVR_HH8_LDI_PM_NEG
2736 This is a 16 bit reloc for the AVR that stores negated 8 bit value
2737 (high 6 bit of 22 bit command address) into 8 bit immediate
2742 This is a 32 bit reloc for the AVR that stores 23 bit value
2756 32 bit PC relative PLT address.
2760 Copy symbol at runtime.
2762 BFD_RELOC_390_GLOB_DAT
2766 BFD_RELOC_390_JMP_SLOT
2770 BFD_RELOC_390_RELATIVE
2772 Adjust by program base.
2776 32 bit PC relative offset to GOT.
2782 BFD_RELOC_390_PC16DBL
2784 PC relative 16 bit shifted by 1.
2786 BFD_RELOC_390_PLT16DBL
2788 16 bit PC rel. PLT shifted by 1.
2790 BFD_RELOC_390_PC32DBL
2792 PC relative 32 bit shifted by 1.
2794 BFD_RELOC_390_PLT32DBL
2796 32 bit PC rel. PLT shifted by 1.
2798 BFD_RELOC_390_GOTPCDBL
2800 32 bit PC rel. GOT shifted by 1.
2808 64 bit PC relative PLT address.
2810 BFD_RELOC_390_GOTENT
2812 32 bit rel. offset to GOT entry.
2815 BFD_RELOC_VTABLE_INHERIT
2817 BFD_RELOC_VTABLE_ENTRY
2819 These two relocations are used by the linker to determine which of
2820 the entries in a C++ virtual function table are actually used. When
2821 the --gc-sections option is given, the linker will zero out the entries
2822 that are not used, so that the code for those functions need not be
2823 included in the output.
2825 VTABLE_INHERIT is a zero-space relocation used to describe to the
2826 linker the inheritence tree of a C++ virtual function table. The
2827 relocation's symbol should be the parent class' vtable, and the
2828 relocation should be located at the child vtable.
2830 VTABLE_ENTRY is a zero-space relocation that describes the use of a
2831 virtual function table entry. The reloc's symbol should refer to the
2832 table of the class mentioned in the code. Off of that base, an offset
2833 describes the entry that is being used. For Rela hosts, this offset
2834 is stored in the reloc's addend. For Rel hosts, we are forced to put
2835 this offset in the reloc's section offset.
2838 BFD_RELOC_IA64_IMM14
2840 BFD_RELOC_IA64_IMM22
2842 BFD_RELOC_IA64_IMM64
2844 BFD_RELOC_IA64_DIR32MSB
2846 BFD_RELOC_IA64_DIR32LSB
2848 BFD_RELOC_IA64_DIR64MSB
2850 BFD_RELOC_IA64_DIR64LSB
2852 BFD_RELOC_IA64_GPREL22
2854 BFD_RELOC_IA64_GPREL64I
2856 BFD_RELOC_IA64_GPREL32MSB
2858 BFD_RELOC_IA64_GPREL32LSB
2860 BFD_RELOC_IA64_GPREL64MSB
2862 BFD_RELOC_IA64_GPREL64LSB
2864 BFD_RELOC_IA64_LTOFF22
2866 BFD_RELOC_IA64_LTOFF64I
2868 BFD_RELOC_IA64_PLTOFF22
2870 BFD_RELOC_IA64_PLTOFF64I
2872 BFD_RELOC_IA64_PLTOFF64MSB
2874 BFD_RELOC_IA64_PLTOFF64LSB
2876 BFD_RELOC_IA64_FPTR64I
2878 BFD_RELOC_IA64_FPTR32MSB
2880 BFD_RELOC_IA64_FPTR32LSB
2882 BFD_RELOC_IA64_FPTR64MSB
2884 BFD_RELOC_IA64_FPTR64LSB
2886 BFD_RELOC_IA64_PCREL21B
2888 BFD_RELOC_IA64_PCREL21BI
2890 BFD_RELOC_IA64_PCREL21M
2892 BFD_RELOC_IA64_PCREL21F
2894 BFD_RELOC_IA64_PCREL22
2896 BFD_RELOC_IA64_PCREL60B
2898 BFD_RELOC_IA64_PCREL64I
2900 BFD_RELOC_IA64_PCREL32MSB
2902 BFD_RELOC_IA64_PCREL32LSB
2904 BFD_RELOC_IA64_PCREL64MSB
2906 BFD_RELOC_IA64_PCREL64LSB
2908 BFD_RELOC_IA64_LTOFF_FPTR22
2910 BFD_RELOC_IA64_LTOFF_FPTR64I
2912 BFD_RELOC_IA64_LTOFF_FPTR64MSB
2914 BFD_RELOC_IA64_LTOFF_FPTR64LSB
2916 BFD_RELOC_IA64_SEGREL32MSB
2918 BFD_RELOC_IA64_SEGREL32LSB
2920 BFD_RELOC_IA64_SEGREL64MSB
2922 BFD_RELOC_IA64_SEGREL64LSB
2924 BFD_RELOC_IA64_SECREL32MSB
2926 BFD_RELOC_IA64_SECREL32LSB
2928 BFD_RELOC_IA64_SECREL64MSB
2930 BFD_RELOC_IA64_SECREL64LSB
2932 BFD_RELOC_IA64_REL32MSB
2934 BFD_RELOC_IA64_REL32LSB
2936 BFD_RELOC_IA64_REL64MSB
2938 BFD_RELOC_IA64_REL64LSB
2940 BFD_RELOC_IA64_LTV32MSB
2942 BFD_RELOC_IA64_LTV32LSB
2944 BFD_RELOC_IA64_LTV64MSB
2946 BFD_RELOC_IA64_LTV64LSB
2948 BFD_RELOC_IA64_IPLTMSB
2950 BFD_RELOC_IA64_IPLTLSB
2954 BFD_RELOC_IA64_TPREL22
2956 BFD_RELOC_IA64_TPREL64MSB
2958 BFD_RELOC_IA64_TPREL64LSB
2960 BFD_RELOC_IA64_LTOFF_TP22
2962 BFD_RELOC_IA64_LTOFF22X
2964 BFD_RELOC_IA64_LDXMOV
2966 Intel IA64 Relocations.
2969 BFD_RELOC_M68HC11_HI8
2971 Motorola 68HC11 reloc.
2972 This is the 8 bits high part of an absolute address.
2974 BFD_RELOC_M68HC11_LO8
2976 Motorola 68HC11 reloc.
2977 This is the 8 bits low part of an absolute address.
2979 BFD_RELOC_M68HC11_3B
2981 Motorola 68HC11 reloc.
2982 This is the 3 bits of a value.
2985 BFD_RELOC_CRIS_BDISP8
2987 BFD_RELOC_CRIS_UNSIGNED_5
2989 BFD_RELOC_CRIS_SIGNED_6
2991 BFD_RELOC_CRIS_UNSIGNED_6
2993 BFD_RELOC_CRIS_UNSIGNED_4
2995 These relocs are only used within the CRIS assembler. They are not
2996 (at present) written to any object files.
3001 BFD_RELOC_860_GLOB_DAT
3003 BFD_RELOC_860_JUMP_SLOT
3005 BFD_RELOC_860_RELATIVE
3015 BFD_RELOC_860_SPLIT0
3019 BFD_RELOC_860_SPLIT1
3023 BFD_RELOC_860_SPLIT2
3027 BFD_RELOC_860_LOGOT0
3029 BFD_RELOC_860_SPGOT0
3031 BFD_RELOC_860_LOGOT1
3033 BFD_RELOC_860_SPGOT1
3035 BFD_RELOC_860_LOGOTOFF0
3037 BFD_RELOC_860_SPGOTOFF0
3039 BFD_RELOC_860_LOGOTOFF1
3041 BFD_RELOC_860_SPGOTOFF1
3043 BFD_RELOC_860_LOGOTOFF2
3045 BFD_RELOC_860_LOGOTOFF3
3049 BFD_RELOC_860_HIGHADJ
3053 BFD_RELOC_860_HAGOTOFF
3061 BFD_RELOC_860_HIGOTOFF
3063 Intel i860 Relocations.
3069 .typedef enum bfd_reloc_code_real bfd_reloc_code_real_type;
3074 bfd_reloc_type_lookup
3078 bfd_reloc_type_lookup (bfd *abfd, bfd_reloc_code_real_type code);
3081 Return a pointer to a howto structure which, when
3082 invoked, will perform the relocation @var{code} on data from the
3088 bfd_reloc_type_lookup (abfd
, code
)
3090 bfd_reloc_code_real_type code
;
3092 return BFD_SEND (abfd
, reloc_type_lookup
, (abfd
, code
));
3095 static reloc_howto_type bfd_howto_32
=
3096 HOWTO (0, 00, 2, 32, false, 0, complain_overflow_bitfield
, 0, "VRT32", false, 0xffffffff, 0xffffffff, true);
3100 bfd_default_reloc_type_lookup
3103 reloc_howto_type *bfd_default_reloc_type_lookup
3104 (bfd *abfd, bfd_reloc_code_real_type code);
3107 Provides a default relocation lookup routine for any architecture.
3112 bfd_default_reloc_type_lookup (abfd
, code
)
3114 bfd_reloc_code_real_type code
;
3118 case BFD_RELOC_CTOR
:
3119 /* The type of reloc used in a ctor, which will be as wide as the
3120 address - so either a 64, 32, or 16 bitter. */
3121 switch (bfd_get_arch_info (abfd
)->bits_per_address
)
3126 return &bfd_howto_32
;
3135 return (reloc_howto_type
*) NULL
;
3140 bfd_get_reloc_code_name
3143 const char *bfd_get_reloc_code_name (bfd_reloc_code_real_type code);
3146 Provides a printable name for the supplied relocation code.
3147 Useful mainly for printing error messages.
3151 bfd_get_reloc_code_name (code
)
3152 bfd_reloc_code_real_type code
;
3154 if (code
> BFD_RELOC_UNUSED
)
3156 return bfd_reloc_code_real_names
[(int)code
];
3161 bfd_generic_relax_section
3164 boolean bfd_generic_relax_section
3167 struct bfd_link_info *,
3171 Provides default handling for relaxing for back ends which
3172 don't do relaxing -- i.e., does nothing.
3177 bfd_generic_relax_section (abfd
, section
, link_info
, again
)
3178 bfd
*abfd ATTRIBUTE_UNUSED
;
3179 asection
*section ATTRIBUTE_UNUSED
;
3180 struct bfd_link_info
*link_info ATTRIBUTE_UNUSED
;
3189 bfd_generic_gc_sections
3192 boolean bfd_generic_gc_sections
3193 (bfd *, struct bfd_link_info *);
3196 Provides default handling for relaxing for back ends which
3197 don't do section gc -- i.e., does nothing.
3202 bfd_generic_gc_sections (abfd
, link_info
)
3203 bfd
*abfd ATTRIBUTE_UNUSED
;
3204 struct bfd_link_info
*link_info ATTRIBUTE_UNUSED
;
3211 bfd_generic_get_relocated_section_contents
3215 bfd_generic_get_relocated_section_contents (bfd *abfd,
3216 struct bfd_link_info *link_info,
3217 struct bfd_link_order *link_order,
3219 boolean relocateable,
3223 Provides default handling of relocation effort for back ends
3224 which can't be bothered to do it efficiently.
3229 bfd_generic_get_relocated_section_contents (abfd
, link_info
, link_order
, data
,
3230 relocateable
, symbols
)
3232 struct bfd_link_info
*link_info
;
3233 struct bfd_link_order
*link_order
;
3235 boolean relocateable
;
3238 /* Get enough memory to hold the stuff */
3239 bfd
*input_bfd
= link_order
->u
.indirect
.section
->owner
;
3240 asection
*input_section
= link_order
->u
.indirect
.section
;
3242 long reloc_size
= bfd_get_reloc_upper_bound (input_bfd
, input_section
);
3243 arelent
**reloc_vector
= NULL
;
3249 reloc_vector
= (arelent
**) bfd_malloc ((size_t) reloc_size
);
3250 if (reloc_vector
== NULL
&& reloc_size
!= 0)
3253 /* read in the section */
3254 if (!bfd_get_section_contents (input_bfd
,
3258 input_section
->_raw_size
))
3261 /* We're not relaxing the section, so just copy the size info */
3262 input_section
->_cooked_size
= input_section
->_raw_size
;
3263 input_section
->reloc_done
= true;
3265 reloc_count
= bfd_canonicalize_reloc (input_bfd
,
3269 if (reloc_count
< 0)
3272 if (reloc_count
> 0)
3275 for (parent
= reloc_vector
; *parent
!= (arelent
*) NULL
;
3278 char *error_message
= (char *) NULL
;
3279 bfd_reloc_status_type r
=
3280 bfd_perform_relocation (input_bfd
,
3284 relocateable
? abfd
: (bfd
*) NULL
,
3289 asection
*os
= input_section
->output_section
;
3291 /* A partial link, so keep the relocs */
3292 os
->orelocation
[os
->reloc_count
] = *parent
;
3296 if (r
!= bfd_reloc_ok
)
3300 case bfd_reloc_undefined
:
3301 if (!((*link_info
->callbacks
->undefined_symbol
)
3302 (link_info
, bfd_asymbol_name (*(*parent
)->sym_ptr_ptr
),
3303 input_bfd
, input_section
, (*parent
)->address
,
3307 case bfd_reloc_dangerous
:
3308 BFD_ASSERT (error_message
!= (char *) NULL
);
3309 if (!((*link_info
->callbacks
->reloc_dangerous
)
3310 (link_info
, error_message
, input_bfd
, input_section
,
3311 (*parent
)->address
)))
3314 case bfd_reloc_overflow
:
3315 if (!((*link_info
->callbacks
->reloc_overflow
)
3316 (link_info
, bfd_asymbol_name (*(*parent
)->sym_ptr_ptr
),
3317 (*parent
)->howto
->name
, (*parent
)->addend
,
3318 input_bfd
, input_section
, (*parent
)->address
)))
3321 case bfd_reloc_outofrange
:
3330 if (reloc_vector
!= NULL
)
3331 free (reloc_vector
);
3335 if (reloc_vector
!= NULL
)
3336 free (reloc_vector
);