1 /* BFD support for handling relocation entries.
2 Copyright (C) 1990, 91, 92, 93, 94, 95, 96, 97, 98, 1999
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-mass 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:
153 | return foo[0x12345678];
156 Could be compiled into:
159 | moveb @@#12345678,d0
165 This could create a reloc pointing to <<foo>>, but leave the
166 offset in the data, something like:
169 |RELOCATION RECORDS FOR [.text]:
173 |00000000 4e56 fffc ; linkw fp,#-4
174 |00000004 1039 1234 5678 ; moveb @@#12345678,d0
175 |0000000a 49c0 ; extbl d0
176 |0000000c 4e5e ; unlk fp
180 Using coff and an 88k, some instructions don't have enough
181 space in them to represent the full address range, and
182 pointers have to be loaded in two parts. So you'd get something like:
185 | or.u r13,r0,hi16(_foo+0x12345678)
186 | ld.b r2,r13,lo16(_foo+0x12345678)
190 This should create two relocs, both pointing to <<_foo>>, and with
191 0x12340000 in their addend field. The data would consist of:
194 |RELOCATION RECORDS FOR [.text]:
196 |00000002 HVRT16 _foo+0x12340000
197 |00000006 LVRT16 _foo+0x12340000
199 |00000000 5da05678 ; or.u r13,r0,0x5678
200 |00000004 1c4d5678 ; ld.b r2,r13,0x5678
201 |00000008 f400c001 ; jmp r1
204 The relocation routine digs out the value from the data, adds
205 it to the addend to get the original offset, and then adds the
206 value of <<_foo>>. Note that all 32 bits have to be kept around
207 somewhere, to cope with carry from bit 15 to bit 16.
209 One further example is the sparc and the a.out format. The
210 sparc has a similar problem to the 88k, in that some
211 instructions don't have room for an entire offset, but on the
212 sparc the parts are created in odd sized lumps. The designers of
213 the a.out format chose to not use the data within the section
214 for storing part of the offset; all the offset is kept within
215 the reloc. Anything in the data should be ignored.
218 | sethi %hi(_foo+0x12345678),%g2
219 | ldsb [%g2+%lo(_foo+0x12345678)],%i0
223 Both relocs contain a pointer to <<foo>>, and the offsets
227 |RELOCATION RECORDS FOR [.text]:
229 |00000004 HI22 _foo+0x12345678
230 |00000008 LO10 _foo+0x12345678
232 |00000000 9de3bf90 ; save %sp,-112,%sp
233 |00000004 05000000 ; sethi %hi(_foo+0),%g2
234 |00000008 f048a000 ; ldsb [%g2+%lo(_foo+0)],%i0
235 |0000000c 81c7e008 ; ret
236 |00000010 81e80000 ; restore
241 The <<howto>> field can be imagined as a
242 relocation instruction. It is a pointer to a structure which
243 contains information on what to do with all of the other
244 information in the reloc record and data section. A back end
245 would normally have a relocation instruction set and turn
246 relocations into pointers to the correct structure on input -
247 but it would be possible to create each howto field on demand.
253 <<enum complain_overflow>>
255 Indicates what sort of overflow checking should be done when
256 performing a relocation.
260 .enum complain_overflow
262 . {* Do not complain on overflow. *}
263 . complain_overflow_dont,
265 . {* Complain if the bitfield overflows, whether it is considered
266 . as signed or unsigned. *}
267 . complain_overflow_bitfield,
269 . {* Complain if the value overflows when considered as signed
271 . complain_overflow_signed,
273 . {* Complain if the value overflows when considered as an
274 . unsigned number. *}
275 . complain_overflow_unsigned
284 The <<reloc_howto_type>> is a structure which contains all the
285 information that libbfd needs to know to tie up a back end's data.
288 .struct symbol_cache_entry; {* Forward declaration *}
290 .struct reloc_howto_struct
292 . {* The type field has mainly a documentary use - the back end can
293 . do what it wants with it, though normally the back end's
294 . external idea of what a reloc number is stored
295 . in this field. For example, a PC relative word relocation
296 . in a coff environment has the type 023 - because that's
297 . what the outside world calls a R_PCRWORD reloc. *}
300 . {* The value the final relocation is shifted right by. This drops
301 . unwanted data from the relocation. *}
302 . unsigned int rightshift;
304 . {* The size of the item to be relocated. This is *not* a
305 . power-of-two measure. To get the number of bytes operated
306 . on by a type of relocation, use bfd_get_reloc_size. *}
309 . {* The number of bits in the item to be relocated. This is used
310 . when doing overflow checking. *}
311 . unsigned int bitsize;
313 . {* Notes that the relocation is relative to the location in the
314 . data section of the addend. The relocation function will
315 . subtract from the relocation value the address of the location
316 . being relocated. *}
317 . boolean pc_relative;
319 . {* The bit position of the reloc value in the destination.
320 . The relocated value is left shifted by this amount. *}
321 . unsigned int bitpos;
323 . {* What type of overflow error should be checked for when
325 . enum complain_overflow complain_on_overflow;
327 . {* If this field is non null, then the supplied function is
328 . called rather than the normal function. This allows really
329 . strange relocation methods to be accomodated (e.g., i960 callj
331 . bfd_reloc_status_type (*special_function)
332 . PARAMS ((bfd *abfd,
333 . arelent *reloc_entry,
334 . struct symbol_cache_entry *symbol,
336 . asection *input_section,
338 . char **error_message));
340 . {* The textual name of the relocation type. *}
343 . {* When performing a partial link, some formats must modify the
344 . relocations rather than the data - this flag signals this.*}
345 . boolean partial_inplace;
347 . {* The src_mask selects which parts of the read in data
348 . are to be used in the relocation sum. E.g., if this was an 8 bit
349 . bit of data which we read and relocated, this would be
350 . 0x000000ff. When we have relocs which have an addend, such as
351 . sun4 extended relocs, the value in the offset part of a
352 . relocating field is garbage so we never use it. In this case
353 . the mask would be 0x00000000. *}
356 . {* The dst_mask selects which parts of the instruction are replaced
357 . into the instruction. In most cases src_mask == dst_mask,
358 . except in the above special case, where dst_mask would be
359 . 0x000000ff, and src_mask would be 0x00000000. *}
362 . {* When some formats create PC relative instructions, they leave
363 . the value of the pc of the place being relocated in the offset
364 . slot of the instruction, so that a PC relative relocation can
365 . be made just by adding in an ordinary offset (e.g., sun3 a.out).
366 . Some formats leave the displacement part of an instruction
367 . empty (e.g., m88k bcs); this flag signals the fact.*}
368 . boolean pcrel_offset;
379 The HOWTO define is horrible and will go away.
382 .#define HOWTO(C, R,S,B, P, BI, O, SF, NAME, INPLACE, MASKSRC, MASKDST, PC) \
383 . {(unsigned)C,R,S,B, P, BI, O,SF,NAME,INPLACE,MASKSRC,MASKDST,PC}
386 And will be replaced with the totally magic way. But for the
387 moment, we are compatible, so do it this way.
390 .#define NEWHOWTO( FUNCTION, NAME,SIZE,REL,IN) HOWTO(0,0,SIZE,0,REL,0,complain_overflow_dont,FUNCTION, NAME,false,0,0,IN)
394 This is used to fill in an empty howto entry in an array.
396 .#define EMPTY_HOWTO(C) \
397 . HOWTO((C),0,0,0,false,0,complain_overflow_dont,NULL,NULL,false,0,0,false)
401 Helper routine to turn a symbol into a relocation value.
403 .#define HOWTO_PREPARE(relocation, symbol) \
405 . if (symbol != (asymbol *)NULL) { \
406 . if (bfd_is_com_section (symbol->section)) { \
410 . relocation = symbol->value; \
422 unsigned int bfd_get_reloc_size (reloc_howto_type *);
425 For a reloc_howto_type that operates on a fixed number of bytes,
426 this returns the number of bytes operated on.
430 bfd_get_reloc_size (howto)
431 reloc_howto_type *howto;
452 How relocs are tied together in an <<asection>>:
454 .typedef struct relent_chain {
456 . struct relent_chain *next;
461 /* N_ONES produces N one bits, without overflowing machine arithmetic. */
462 #define N_ONES(n) (((((bfd_vma) 1 << ((n) - 1)) - 1) << 1) | 1)
469 bfd_reloc_status_type
471 (enum complain_overflow how,
472 unsigned int bitsize,
473 unsigned int rightshift,
474 unsigned int addrsize,
478 Perform overflow checking on @var{relocation} which has
479 @var{bitsize} significant bits and will be shifted right by
480 @var{rightshift} bits, on a machine with addresses containing
481 @var{addrsize} significant bits. The result is either of
482 @code{bfd_reloc_ok} or @code{bfd_reloc_overflow}.
486 bfd_reloc_status_type
487 bfd_check_overflow (how, bitsize, rightshift, addrsize, relocation)
488 enum complain_overflow how;
489 unsigned int bitsize;
490 unsigned int rightshift;
491 unsigned int addrsize;
494 bfd_vma fieldmask, addrmask, signmask, ss, a;
495 bfd_reloc_status_type flag = bfd_reloc_ok;
499 /* Note: BITSIZE should always be <= ADDRSIZE, but in case it's not,
500 we'll be permissive: extra bits in the field mask will
501 automatically extend the address mask for purposes of the
503 fieldmask = N_ONES (bitsize);
504 addrmask = N_ONES (addrsize) | fieldmask;
508 case complain_overflow_dont:
511 case complain_overflow_signed:
512 /* If any sign bits are set, all sign bits must be set. That
513 is, A must be a valid negative address after shifting. */
514 a = (a & addrmask) >> rightshift;
515 signmask = ~ (fieldmask >> 1);
517 if (ss != 0 && ss != ((addrmask >> rightshift) & signmask))
518 flag = bfd_reloc_overflow;
521 case complain_overflow_unsigned:
522 /* We have an overflow if the address does not fit in the field. */
523 a = (a & addrmask) >> rightshift;
524 if ((a & ~ fieldmask) != 0)
525 flag = bfd_reloc_overflow;
528 case complain_overflow_bitfield:
529 /* Bitfields are sometimes signed, sometimes unsigned. We
530 overflow if the value has some, but not all, bits set outside
531 the field, or if it has any bits set outside the field but
532 the sign bit is not set. */
534 if ((a & ~ fieldmask) != 0)
536 signmask = (fieldmask >> 1) + 1;
537 ss = (signmask << rightshift) - 1;
538 if ((ss | relocation) != ~ (bfd_vma) 0)
539 flag = bfd_reloc_overflow;
552 bfd_perform_relocation
555 bfd_reloc_status_type
556 bfd_perform_relocation
558 arelent *reloc_entry,
560 asection *input_section,
562 char **error_message);
565 If @var{output_bfd} is supplied to this function, the
566 generated image will be relocatable; the relocations are
567 copied to the output file after they have been changed to
568 reflect the new state of the world. There are two ways of
569 reflecting the results of partial linkage in an output file:
570 by modifying the output data in place, and by modifying the
571 relocation record. Some native formats (e.g., basic a.out and
572 basic coff) have no way of specifying an addend in the
573 relocation type, so the addend has to go in the output data.
574 This is no big deal since in these formats the output data
575 slot will always be big enough for the addend. Complex reloc
576 types with addends were invented to solve just this problem.
577 The @var{error_message} argument is set to an error message if
578 this return @code{bfd_reloc_dangerous}.
583 bfd_reloc_status_type
584 bfd_perform_relocation (abfd, reloc_entry, data, input_section, output_bfd,
587 arelent *reloc_entry;
589 asection *input_section;
591 char **error_message;
594 bfd_reloc_status_type flag = bfd_reloc_ok;
595 bfd_size_type addr = reloc_entry->address;
596 bfd_vma output_base = 0;
597 reloc_howto_type *howto = reloc_entry->howto;
598 asection *reloc_target_output_section;
601 symbol = *(reloc_entry->sym_ptr_ptr);
602 if (bfd_is_abs_section (symbol->section)
603 && output_bfd != (bfd *) NULL)
605 reloc_entry->address += input_section->output_offset;
609 /* If we are not producing relocateable output, return an error if
610 the symbol is not defined. An undefined weak symbol is
611 considered to have a value of zero (SVR4 ABI, p. 4-27). */
612 if (bfd_is_und_section (symbol->section)
613 && (symbol->flags & BSF_WEAK) == 0
614 && output_bfd == (bfd *) NULL)
615 flag = bfd_reloc_undefined;
617 /* If there is a function supplied to handle this relocation type,
618 call it. It'll return `bfd_reloc_continue' if further processing
620 if (howto->special_function)
622 bfd_reloc_status_type cont;
623 cont = howto->special_function (abfd, reloc_entry, symbol, data,
624 input_section, output_bfd,
626 if (cont != bfd_reloc_continue)
630 /* Is the address of the relocation really within the section? */
631 if (reloc_entry->address > input_section->_cooked_size)
632 return bfd_reloc_outofrange;
634 /* Work out which section the relocation is targetted at and the
635 initial relocation command value. */
637 /* Get symbol value. (Common symbols are special.) */
638 if (bfd_is_com_section (symbol->section))
641 relocation = symbol->value;
644 reloc_target_output_section = symbol->section->output_section;
646 /* Convert input-section-relative symbol value to absolute. */
647 if (output_bfd && howto->partial_inplace == false)
650 output_base = reloc_target_output_section->vma;
652 relocation += output_base + symbol->section->output_offset;
654 /* Add in supplied addend. */
655 relocation += reloc_entry->addend;
657 /* Here the variable relocation holds the final address of the
658 symbol we are relocating against, plus any addend. */
660 if (howto->pc_relative == true)
662 /* This is a PC relative relocation. We want to set RELOCATION
663 to the distance between the address of the symbol and the
664 location. RELOCATION is already the address of the symbol.
666 We start by subtracting the address of the section containing
669 If pcrel_offset is set, we must further subtract the position
670 of the location within the section. Some targets arrange for
671 the addend to be the negative of the position of the location
672 within the section; for example, i386-aout does this. For
673 i386-aout, pcrel_offset is false. Some other targets do not
674 include the position of the location; for example, m88kbcs,
675 or ELF. For those targets, pcrel_offset is true.
677 If we are producing relocateable output, then we must ensure
678 that this reloc will be correctly computed when the final
679 relocation is done. If pcrel_offset is false we want to wind
680 up with the negative of the location within the section,
681 which means we must adjust the existing addend by the change
682 in the location within the section. If pcrel_offset is true
683 we do not want to adjust the existing addend at all.
685 FIXME: This seems logical to me, but for the case of
686 producing relocateable output it is not what the code
687 actually does. I don't want to change it, because it seems
688 far too likely that something will break. */
691 input_section->output_section->vma + input_section->output_offset;
693 if (howto->pcrel_offset == true)
694 relocation -= reloc_entry->address;
697 if (output_bfd != (bfd *) NULL)
699 if (howto->partial_inplace == false)
701 /* This is a partial relocation, and we want to apply the relocation
702 to the reloc entry rather than the raw data. Modify the reloc
703 inplace to reflect what we now know. */
704 reloc_entry->addend = relocation;
705 reloc_entry->address += input_section->output_offset;
710 /* This is a partial relocation, but inplace, so modify the
713 If we've relocated with a symbol with a section, change
714 into a ref to the section belonging to the symbol. */
716 reloc_entry->address += input_section->output_offset;
719 if (abfd->xvec->flavour == bfd_target_coff_flavour
720 && strcmp (abfd->xvec->name, "aixcoff-rs6000") != 0
721 && strcmp (abfd->xvec->name, "xcoff-powermac") != 0
722 && strcmp (abfd->xvec->name, "coff-Intel-little") != 0
723 && strcmp (abfd->xvec->name, "coff-Intel-big") != 0)
726 /* For m68k-coff, the addend was being subtracted twice during
727 relocation with -r. Removing the line below this comment
728 fixes that problem; see PR 2953.
730 However, Ian wrote the following, regarding removing the line below,
731 which explains why it is still enabled: --djm
733 If you put a patch like that into BFD you need to check all the COFF
734 linkers. I am fairly certain that patch will break coff-i386 (e.g.,
735 SCO); see coff_i386_reloc in coff-i386.c where I worked around the
736 problem in a different way. There may very well be a reason that the
737 code works as it does.
739 Hmmm. The first obvious point is that bfd_perform_relocation should
740 not have any tests that depend upon the flavour. It's seem like
741 entirely the wrong place for such a thing. The second obvious point
742 is that the current code ignores the reloc addend when producing
743 relocateable output for COFF. That's peculiar. In fact, I really
744 have no idea what the point of the line you want to remove is.
746 A typical COFF reloc subtracts the old value of the symbol and adds in
747 the new value to the location in the object file (if it's a pc
748 relative reloc it adds the difference between the symbol value and the
749 location). When relocating we need to preserve that property.
751 BFD handles this by setting the addend to the negative of the old
752 value of the symbol. Unfortunately it handles common symbols in a
753 non-standard way (it doesn't subtract the old value) but that's a
754 different story (we can't change it without losing backward
755 compatibility with old object files) (coff-i386 does subtract the old
756 value, to be compatible with existing coff-i386 targets, like SCO).
758 So everything works fine when not producing relocateable output. When
759 we are producing relocateable output, logically we should do exactly
760 what we do when not producing relocateable output. Therefore, your
761 patch is correct. In fact, it should probably always just set
762 reloc_entry->addend to 0 for all cases, since it is, in fact, going to
763 add the value into the object file. This won't hurt the COFF code,
764 which doesn't use the addend; I'm not sure what it will do to other
765 formats (the thing to check for would be whether any formats both use
766 the addend and set partial_inplace).
768 When I wanted to make coff-i386 produce relocateable output, I ran
769 into the problem that you are running into: I wanted to remove that
770 line. Rather than risk it, I made the coff-i386 relocs use a special
771 function; it's coff_i386_reloc in coff-i386.c. The function
772 specifically adds the addend field into the object file, knowing that
773 bfd_perform_relocation is not going to. If you remove that line, then
774 coff-i386.c will wind up adding the addend field in twice. It's
775 trivial to fix; it just needs to be done.
777 The problem with removing the line is just that it may break some
778 working code. With BFD it's hard to be sure of anything. The right
779 way to deal with this is simply to build and test at least all the
780 supported COFF targets. It should be straightforward if time and disk
781 space consuming. For each target:
783 2) generate some executable, and link it using -r (I would
784 probably use paranoia.o and link against newlib/libc.a, which
785 for all the supported targets would be available in
786 /usr/cygnus/progressive/H-host/target/lib/libc.a).
787 3) make the change to reloc.c
788 4) rebuild the linker
790 6) if the resulting object files are the same, you have at least
792 7) if they are different you have to figure out which version is
795 relocation -= reloc_entry->addend;
797 reloc_entry->addend = 0;
801 reloc_entry->addend = relocation;
807 reloc_entry->addend = 0;
810 /* FIXME: This overflow checking is incomplete, because the value
811 might have overflowed before we get here. For a correct check we
812 need to compute the value in a size larger than bitsize, but we
813 can't reasonably do that for a reloc the same size as a host
815 FIXME: We should also do overflow checking on the result after
816 adding in the value contained in the object file. */
817 if (howto->complain_on_overflow != complain_overflow_dont
818 && flag == bfd_reloc_ok)
819 flag = bfd_check_overflow (howto->complain_on_overflow,
822 bfd_arch_bits_per_address (abfd),
826 Either we are relocating all the way, or we don't want to apply
827 the relocation to the reloc entry (probably because there isn't
828 any room in the output format to describe addends to relocs)
831 /* The cast to bfd_vma avoids a bug in the Alpha OSF/1 C compiler
832 (OSF version 1.3, compiler version 3.11). It miscompiles the
846 x <<= (unsigned long) s.i0;
850 printf ("succeeded (%lx)\n", x);
854 relocation >>= (bfd_vma) howto->rightshift;
856 /* Shift everything up to where it's going to be used */
858 relocation <<= (bfd_vma) howto->bitpos;
860 /* Wait for the day when all have the mask in them */
863 i instruction to be left alone
864 o offset within instruction
865 r relocation offset to apply
874 i i i i i o o o o o from bfd_get<size>
875 and S S S S S to get the size offset we want
876 + r r r r r r r r r r to get the final value to place
877 and D D D D D to chop to right size
878 -----------------------
881 ... i i i i i o o o o o from bfd_get<size>
882 and N N N N N get instruction
883 -----------------------
889 -----------------------
890 R R R R R R R R R R put into bfd_put<size>
894 x = ( (x & ~howto->dst_mask) | (((x & howto->src_mask) + relocation) & howto->dst_mask))
900 char x = bfd_get_8 (abfd, (char *) data + addr);
902 bfd_put_8 (abfd, x, (unsigned char *) data + addr);
908 short x = bfd_get_16 (abfd, (bfd_byte *) data + addr);
910 bfd_put_16 (abfd, x, (unsigned char *) data + addr);
915 long x = bfd_get_32 (abfd, (bfd_byte *) data + addr);
917 bfd_put_32 (abfd, x, (bfd_byte *) data + addr);
922 long x = bfd_get_32 (abfd, (bfd_byte *) data + addr);
923 relocation = -relocation;
925 bfd_put_32 (abfd, x, (bfd_byte *) data + addr);
931 long x = bfd_get_16 (abfd, (bfd_byte *) data + addr);
932 relocation = -relocation;
934 bfd_put_16 (abfd, x, (bfd_byte *) data + addr);
945 bfd_vma x = bfd_get_64 (abfd, (bfd_byte *) data + addr);
947 bfd_put_64 (abfd, x, (bfd_byte *) data + addr);
954 return bfd_reloc_other;
962 bfd_install_relocation
965 bfd_reloc_status_type
966 bfd_install_relocation
968 arelent *reloc_entry,
969 PTR data, bfd_vma data_start,
970 asection *input_section,
971 char **error_message);
974 This looks remarkably like <<bfd_perform_relocation>>, except it
975 does not expect that the section contents have been filled in.
976 I.e., it's suitable for use when creating, rather than applying
979 For now, this function should be considered reserved for the
985 bfd_reloc_status_type
986 bfd_install_relocation (abfd, reloc_entry, data_start, data_start_offset,
987 input_section, error_message)
989 arelent *reloc_entry;
991 bfd_vma data_start_offset;
992 asection *input_section;
993 char **error_message;
996 bfd_reloc_status_type flag = bfd_reloc_ok;
997 bfd_size_type addr = reloc_entry->address;
998 bfd_vma output_base = 0;
999 reloc_howto_type *howto = reloc_entry->howto;
1000 asection *reloc_target_output_section;
1004 symbol = *(reloc_entry->sym_ptr_ptr);
1005 if (bfd_is_abs_section (symbol->section))
1007 reloc_entry->address += input_section->output_offset;
1008 return bfd_reloc_ok;
1011 /* If there is a function supplied to handle this relocation type,
1012 call it. It'll return `bfd_reloc_continue' if further processing
1014 if (howto->special_function)
1016 bfd_reloc_status_type cont;
1018 /* XXX - The special_function calls haven't been fixed up to deal
1019 with creating new relocations and section contents. */
1020 cont = howto->special_function (abfd, reloc_entry, symbol,
1021 /* XXX - Non-portable! */
1022 ((bfd_byte *) data_start
1023 - data_start_offset),
1024 input_section, abfd, error_message);
1025 if (cont != bfd_reloc_continue)
1029 /* Is the address of the relocation really within the section? */
1030 if (reloc_entry->address > input_section->_cooked_size)
1031 return bfd_reloc_outofrange;
1033 /* Work out which section the relocation is targetted at and the
1034 initial relocation command value. */
1036 /* Get symbol value. (Common symbols are special.) */
1037 if (bfd_is_com_section (symbol->section))
1040 relocation = symbol->value;
1042 reloc_target_output_section = symbol->section->output_section;
1044 /* Convert input-section-relative symbol value to absolute. */
1045 if (howto->partial_inplace == false)
1048 output_base = reloc_target_output_section->vma;
1050 relocation += output_base + symbol->section->output_offset;
1052 /* Add in supplied addend. */
1053 relocation += reloc_entry->addend;
1055 /* Here the variable relocation holds the final address of the
1056 symbol we are relocating against, plus any addend. */
1058 if (howto->pc_relative == true)
1060 /* This is a PC relative relocation. We want to set RELOCATION
1061 to the distance between the address of the symbol and the
1062 location. RELOCATION is already the address of the symbol.
1064 We start by subtracting the address of the section containing
1067 If pcrel_offset is set, we must further subtract the position
1068 of the location within the section. Some targets arrange for
1069 the addend to be the negative of the position of the location
1070 within the section; for example, i386-aout does this. For
1071 i386-aout, pcrel_offset is false. Some other targets do not
1072 include the position of the location; for example, m88kbcs,
1073 or ELF. For those targets, pcrel_offset is true.
1075 If we are producing relocateable output, then we must ensure
1076 that this reloc will be correctly computed when the final
1077 relocation is done. If pcrel_offset is false we want to wind
1078 up with the negative of the location within the section,
1079 which means we must adjust the existing addend by the change
1080 in the location within the section. If pcrel_offset is true
1081 we do not want to adjust the existing addend at all.
1083 FIXME: This seems logical to me, but for the case of
1084 producing relocateable output it is not what the code
1085 actually does. I don't want to change it, because it seems
1086 far too likely that something will break. */
1089 input_section->output_section->vma + input_section->output_offset;
1091 if (howto->pcrel_offset == true && howto->partial_inplace == true)
1092 relocation -= reloc_entry->address;
1095 if (howto->partial_inplace == false)
1097 /* This is a partial relocation, and we want to apply the relocation
1098 to the reloc entry rather than the raw data. Modify the reloc
1099 inplace to reflect what we now know. */
1100 reloc_entry->addend = relocation;
1101 reloc_entry->address += input_section->output_offset;
1106 /* This is a partial relocation, but inplace, so modify the
1109 If we've relocated with a symbol with a section, change
1110 into a ref to the section belonging to the symbol. */
1112 reloc_entry->address += input_section->output_offset;
1115 if (abfd->xvec->flavour == bfd_target_coff_flavour
1116 && strcmp (abfd->xvec->name, "aixcoff-rs6000") != 0
1117 && strcmp (abfd->xvec->name, "xcoff-powermac") != 0
1118 && strcmp (abfd->xvec->name, "coff-Intel-little") != 0
1119 && strcmp (abfd->xvec->name, "coff-Intel-big") != 0)
1122 /* For m68k-coff, the addend was being subtracted twice during
1123 relocation with -r. Removing the line below this comment
1124 fixes that problem; see PR 2953.
1126 However, Ian wrote the following, regarding removing the line below,
1127 which explains why it is still enabled: --djm
1129 If you put a patch like that into BFD you need to check all the COFF
1130 linkers. I am fairly certain that patch will break coff-i386 (e.g.,
1131 SCO); see coff_i386_reloc in coff-i386.c where I worked around the
1132 problem in a different way. There may very well be a reason that the
1133 code works as it does.
1135 Hmmm. The first obvious point is that bfd_install_relocation should
1136 not have any tests that depend upon the flavour. It's seem like
1137 entirely the wrong place for such a thing. The second obvious point
1138 is that the current code ignores the reloc addend when producing
1139 relocateable output for COFF. That's peculiar. In fact, I really
1140 have no idea what the point of the line you want to remove is.
1142 A typical COFF reloc subtracts the old value of the symbol and adds in
1143 the new value to the location in the object file (if it's a pc
1144 relative reloc it adds the difference between the symbol value and the
1145 location). When relocating we need to preserve that property.
1147 BFD handles this by setting the addend to the negative of the old
1148 value of the symbol. Unfortunately it handles common symbols in a
1149 non-standard way (it doesn't subtract the old value) but that's a
1150 different story (we can't change it without losing backward
1151 compatibility with old object files) (coff-i386 does subtract the old
1152 value, to be compatible with existing coff-i386 targets, like SCO).
1154 So everything works fine when not producing relocateable output. When
1155 we are producing relocateable output, logically we should do exactly
1156 what we do when not producing relocateable output. Therefore, your
1157 patch is correct. In fact, it should probably always just set
1158 reloc_entry->addend to 0 for all cases, since it is, in fact, going to
1159 add the value into the object file. This won't hurt the COFF code,
1160 which doesn't use the addend; I'm not sure what it will do to other
1161 formats (the thing to check for would be whether any formats both use
1162 the addend and set partial_inplace).
1164 When I wanted to make coff-i386 produce relocateable output, I ran
1165 into the problem that you are running into: I wanted to remove that
1166 line. Rather than risk it, I made the coff-i386 relocs use a special
1167 function; it's coff_i386_reloc in coff-i386.c. The function
1168 specifically adds the addend field into the object file, knowing that
1169 bfd_install_relocation is not going to. If you remove that line, then
1170 coff-i386.c will wind up adding the addend field in twice. It's
1171 trivial to fix; it just needs to be done.
1173 The problem with removing the line is just that it may break some
1174 working code. With BFD it's hard to be sure of anything. The right
1175 way to deal with this is simply to build and test at least all the
1176 supported COFF targets. It should be straightforward if time and disk
1177 space consuming. For each target:
1179 2) generate some executable, and link it using -r (I would
1180 probably use paranoia.o and link against newlib/libc.a, which
1181 for all the supported targets would be available in
1182 /usr/cygnus/progressive/H-host/target/lib/libc.a).
1183 3) make the change to reloc.c
1184 4) rebuild the linker
1186 6) if the resulting object files are the same, you have at least
1188 7) if they are different you have to figure out which version is
1191 relocation -= reloc_entry->addend;
1193 reloc_entry->addend = 0;
1197 reloc_entry->addend = relocation;
1201 /* FIXME: This overflow checking is incomplete, because the value
1202 might have overflowed before we get here. For a correct check we
1203 need to compute the value in a size larger than bitsize, but we
1204 can't reasonably do that for a reloc the same size as a host
1206 FIXME: We should also do overflow checking on the result after
1207 adding in the value contained in the object file. */
1208 if (howto->complain_on_overflow != complain_overflow_dont)
1209 flag = bfd_check_overflow (howto->complain_on_overflow,
1212 bfd_arch_bits_per_address (abfd),
1216 Either we are relocating all the way, or we don't want to apply
1217 the relocation to the reloc entry (probably because there isn't
1218 any room in the output format to describe addends to relocs)
1221 /* The cast to bfd_vma avoids a bug in the Alpha OSF/1 C compiler
1222 (OSF version 1.3, compiler version 3.11). It miscompiles the
1236 x <<= (unsigned long) s.i0;
1238 printf ("failed\n");
1240 printf ("succeeded (%lx)\n", x);
1244 relocation >>= (bfd_vma) howto->rightshift;
1246 /* Shift everything up to where it's going to be used */
1248 relocation <<= (bfd_vma) howto->bitpos;
1250 /* Wait for the day when all have the mask in them */
1253 i instruction to be left alone
1254 o offset within instruction
1255 r relocation offset to apply
1264 i i i i i o o o o o from bfd_get<size>
1265 and S S S S S to get the size offset we want
1266 + r r r r r r r r r r to get the final value to place
1267 and D D D D D to chop to right size
1268 -----------------------
1271 ... i i i i i o o o o o from bfd_get<size>
1272 and N N N N N get instruction
1273 -----------------------
1279 -----------------------
1280 R R R R R R R R R R put into bfd_put<size>
1284 x = ( (x & ~howto->dst_mask) | (((x & howto->src_mask) + relocation) & howto->dst_mask))
1286 data = (bfd_byte *) data_start + (addr - data_start_offset);
1288 switch (howto->size)
1292 char x = bfd_get_8 (abfd, (char *) data);
1294 bfd_put_8 (abfd, x, (unsigned char *) data);
1300 short x = bfd_get_16 (abfd, (bfd_byte *) data);
1302 bfd_put_16 (abfd, x, (unsigned char *) data);
1307 long x = bfd_get_32 (abfd, (bfd_byte *) data);
1309 bfd_put_32 (abfd, x, (bfd_byte *) data);
1314 long x = bfd_get_32 (abfd, (bfd_byte *) data);
1315 relocation = -relocation;
1317 bfd_put_32 (abfd, x, (bfd_byte *) data);
1327 bfd_vma x = bfd_get_64 (abfd, (bfd_byte *) data);
1329 bfd_put_64 (abfd, x, (bfd_byte *) data);
1333 return bfd_reloc_other;
1339 /* This relocation routine is used by some of the backend linkers.
1340 They do not construct asymbol or arelent structures, so there is no
1341 reason for them to use bfd_perform_relocation. Also,
1342 bfd_perform_relocation is so hacked up it is easier to write a new
1343 function than to try to deal with it.
1345 This routine does a final relocation. Whether it is useful for a
1346 relocateable link depends upon how the object format defines
1349 FIXME: This routine ignores any special_function in the HOWTO,
1350 since the existing special_function values have been written for
1351 bfd_perform_relocation.
1353 HOWTO is the reloc howto information.
1354 INPUT_BFD is the BFD which the reloc applies to.
1355 INPUT_SECTION is the section which the reloc applies to.
1356 CONTENTS is the contents of the section.
1357 ADDRESS is the address of the reloc within INPUT_SECTION.
1358 VALUE is the value of the symbol the reloc refers to.
1359 ADDEND is the addend of the reloc. */
1361 bfd_reloc_status_type
1362 _bfd_final_link_relocate (howto, input_bfd, input_section, contents, address,
1364 reloc_howto_type *howto;
1366 asection *input_section;
1374 /* Sanity check the address. */
1375 if (address > input_section->_raw_size)
1376 return bfd_reloc_outofrange;
1378 /* This function assumes that we are dealing with a basic relocation
1379 against a symbol. We want to compute the value of the symbol to
1380 relocate to. This is just VALUE, the value of the symbol, plus
1381 ADDEND, any addend associated with the reloc. */
1382 relocation = value + addend;
1384 /* If the relocation is PC relative, we want to set RELOCATION to
1385 the distance between the symbol (currently in RELOCATION) and the
1386 location we are relocating. Some targets (e.g., i386-aout)
1387 arrange for the contents of the section to be the negative of the
1388 offset of the location within the section; for such targets
1389 pcrel_offset is false. Other targets (e.g., m88kbcs or ELF)
1390 simply leave the contents of the section as zero; for such
1391 targets pcrel_offset is true. If pcrel_offset is false we do not
1392 need to subtract out the offset of the location within the
1393 section (which is just ADDRESS). */
1394 if (howto->pc_relative)
1396 relocation -= (input_section->output_section->vma
1397 + input_section->output_offset);
1398 if (howto->pcrel_offset)
1399 relocation -= address;
1402 return _bfd_relocate_contents (howto, input_bfd, relocation,
1403 contents + address);
1406 /* Relocate a given location using a given value and howto. */
1408 bfd_reloc_status_type
1409 _bfd_relocate_contents (howto, input_bfd, relocation, location)
1410 reloc_howto_type *howto;
1418 unsigned int rightshift = howto->rightshift;
1419 unsigned int bitpos = howto->bitpos;
1421 /* If the size is negative, negate RELOCATION. This isn't very
1423 if (howto->size < 0)
1424 relocation = -relocation;
1426 /* Get the value we are going to relocate. */
1427 size = bfd_get_reloc_size (howto);
1434 x = bfd_get_8 (input_bfd, location);
1437 x = bfd_get_16 (input_bfd, location);
1440 x = bfd_get_32 (input_bfd, location);
1444 x = bfd_get_64 (input_bfd, location);
1451 /* Check for overflow. FIXME: We may drop bits during the addition
1452 which we don't check for. We must either check at every single
1453 operation, which would be tedious, or we must do the computations
1454 in a type larger than bfd_vma, which would be inefficient. */
1456 if (howto->complain_on_overflow != complain_overflow_dont)
1458 bfd_vma addrmask, fieldmask, signmask, ss;
1461 /* Get the values to be added together. For signed and unsigned
1462 relocations, we assume that all values should be truncated to
1463 the size of an address. For bitfields, all the bits matter.
1464 See also bfd_check_overflow. */
1465 fieldmask = N_ONES (howto->bitsize);
1466 addrmask = N_ONES (bfd_arch_bits_per_address (input_bfd)) | fieldmask;
1468 b = x & howto->src_mask;
1470 switch (howto->complain_on_overflow)
1472 case complain_overflow_signed:
1473 a = (a & addrmask) >> rightshift;
1475 /* If any sign bits are set, all sign bits must be set.
1476 That is, A must be a valid negative address after
1478 signmask = ~ (fieldmask >> 1);
1480 if (ss != 0 && ss != ((addrmask >> rightshift) & signmask))
1483 /* We only need this next bit of code if the sign bit of B
1484 is below the sign bit of A. This would only happen if
1485 SRC_MASK had fewer bits than BITSIZE. Note that if
1486 SRC_MASK has more bits than BITSIZE, we can get into
1487 trouble; we would need to verify that B is in range, as
1488 we do for A above. */
1489 signmask = ((~ howto->src_mask) >> 1) & howto->src_mask;
1490 if ((b & signmask) != 0)
1492 /* Set all the bits above the sign bit. */
1493 b -= signmask <<= 1;
1496 b = (b & addrmask) >> bitpos;
1498 /* Now we can do the addition. */
1501 /* See if the result has the correct sign. Bits above the
1502 sign bit are junk now; ignore them. If the sum is
1503 positive, make sure we did not have all negative inputs;
1504 if the sum is negative, make sure we did not have all
1505 positive inputs. The test below looks only at the sign
1506 bits, and it really just
1507 SIGN (A) == SIGN (B) && SIGN (A) != SIGN (SUM)
1509 signmask = (fieldmask >> 1) + 1;
1510 if (((~ (a ^ b)) & (a ^ sum)) & signmask)
1515 case complain_overflow_unsigned:
1516 /* Checking for an unsigned overflow is relatively easy:
1517 trim the addresses and add, and trim the result as well.
1518 Overflow is normally indicated when the result does not
1519 fit in the field. However, we also need to consider the
1520 case when, e.g., fieldmask is 0x7fffffff or smaller, an
1521 input is 0x80000000, and bfd_vma is only 32 bits; then we
1522 will get sum == 0, but there is an overflow, since the
1523 inputs did not fit in the field. Instead of doing a
1524 separate test, we can check for this by or-ing in the
1525 operands when testing for the sum overflowing its final
1527 a = (a & addrmask) >> rightshift;
1528 b = (b & addrmask) >> bitpos;
1529 sum = (a + b) & addrmask;
1530 if ((a | b | sum) & ~ fieldmask)
1535 case complain_overflow_bitfield:
1536 /* Much like unsigned, except no trimming with addrmask. In
1537 addition, the sum overflows if there is a carry out of
1538 the bfd_vma, i.e., the sum is less than either input
1543 /* Bitfields are sometimes used for signed numbers; for
1544 example, a 13-bit field sometimes represents values in
1545 0..8191 and sometimes represents values in -4096..4095.
1546 If the field is signed and a is -4095 (0x1001) and b is
1547 -1 (0x1fff), the sum is -4096 (0x1000), but (0x1001 +
1548 0x1fff is 0x3000). It's not clear how to handle this
1549 everywhere, since there is not way to know how many bits
1550 are significant in the relocation, but the original code
1551 assumed that it was fully sign extended, and we will keep
1553 signmask = (fieldmask >> 1) + 1;
1555 if ((a & ~ fieldmask) != 0)
1557 /* Some bits out of the field are set. This might not
1558 be a problem: if this is a signed bitfield, it is OK
1559 iff all the high bits are set, including the sign
1560 bit. We'll try setting all but the most significant
1561 bit in the original relocation value: if this is all
1562 ones, we are OK, assuming a signed bitfield. */
1563 ss = (signmask << rightshift) - 1;
1564 if ((ss | relocation) != ~ (bfd_vma) 0)
1569 /* We just assume (b & ~ fieldmask) == 0. */
1571 /* We explicitly permit wrap around if this relocation
1572 covers the high bit of an address. The Linux kernel
1573 relies on it, and it is the only way to write assembler
1574 code which can run when loaded at a location 0x80000000
1575 away from the location at which it is linked. */
1576 if (howto->bitsize + rightshift
1577 == bfd_arch_bits_per_address (input_bfd))
1581 if (sum < a || (sum & ~ fieldmask) != 0)
1583 /* There was a carry out, or the field overflow. Test
1584 for signed operands again. Here is the overflow test
1585 is as for complain_overflow_signed. */
1586 if (((~ (a ^ b)) & (a ^ sum)) & signmask)
1597 /* Put RELOCATION in the right bits. */
1598 relocation >>= (bfd_vma) rightshift;
1599 relocation <<= (bfd_vma) bitpos;
1601 /* Add RELOCATION to the right bits of X. */
1602 x = ((x & ~howto->dst_mask)
1603 | (((x & howto->src_mask) + relocation) & howto->dst_mask));
1605 /* Put the relocated value back in the object file. */
1612 bfd_put_8 (input_bfd, x, location);
1615 bfd_put_16 (input_bfd, x, location);
1618 bfd_put_32 (input_bfd, x, location);
1622 bfd_put_64 (input_bfd, x, location);
1629 return overflow ? bfd_reloc_overflow : bfd_reloc_ok;
1635 howto manager, , typedef arelent, Relocations
1640 When an application wants to create a relocation, but doesn't
1641 know what the target machine might call it, it can find out by
1642 using this bit of code.
1651 The insides of a reloc code. The idea is that, eventually, there
1652 will be one enumerator for every type of relocation we ever do.
1653 Pass one of these values to <<bfd_reloc_type_lookup>>, and it'll
1654 return a howto pointer.
1656 This does mean that the application must determine the correct
1657 enumerator value; you can't get a howto pointer from a random set
1678 Basic absolute relocations of N bits.
1693 PC-relative relocations. Sometimes these are relative to the address
1694 of the relocation itself; sometimes they are relative to the start of
1695 the section containing the relocation. It depends on the specific target.
1697 The 24-bit relocation is used in some Intel 960 configurations.
1700 BFD_RELOC_32_GOT_PCREL
1702 BFD_RELOC_16_GOT_PCREL
1704 BFD_RELOC_8_GOT_PCREL
1710 BFD_RELOC_LO16_GOTOFF
1712 BFD_RELOC_HI16_GOTOFF
1714 BFD_RELOC_HI16_S_GOTOFF
1718 BFD_RELOC_32_PLT_PCREL
1720 BFD_RELOC_24_PLT_PCREL
1722 BFD_RELOC_16_PLT_PCREL
1724 BFD_RELOC_8_PLT_PCREL
1730 BFD_RELOC_LO16_PLTOFF
1732 BFD_RELOC_HI16_PLTOFF
1734 BFD_RELOC_HI16_S_PLTOFF
1741 BFD_RELOC_68K_GLOB_DAT
1743 BFD_RELOC_68K_JMP_SLOT
1745 BFD_RELOC_68K_RELATIVE
1747 Relocations used by 68K ELF.
1750 BFD_RELOC_32_BASEREL
1752 BFD_RELOC_16_BASEREL
1754 BFD_RELOC_LO16_BASEREL
1756 BFD_RELOC_HI16_BASEREL
1758 BFD_RELOC_HI16_S_BASEREL
1764 Linkage-table relative.
1769 Absolute 8-bit relocation, but used to form an address like 0xFFnn.
1772 BFD_RELOC_32_PCREL_S2
1774 BFD_RELOC_16_PCREL_S2
1776 BFD_RELOC_23_PCREL_S2
1778 These PC-relative relocations are stored as word displacements --
1779 i.e., byte displacements shifted right two bits. The 30-bit word
1780 displacement (<<32_PCREL_S2>> -- 32 bits, shifted 2) is used on the
1781 SPARC. (SPARC tools generally refer to this as <<WDISP30>>.) The
1782 signed 16-bit displacement is used on the MIPS, and the 23-bit
1783 displacement is used on the Alpha.
1790 High 22 bits and low 10 bits of 32-bit value, placed into lower bits of
1791 the target word. These are used on the SPARC.
1798 For systems that allocate a Global Pointer register, these are
1799 displacements off that register. These relocation types are
1800 handled specially, because the value the register will have is
1801 decided relatively late.
1805 BFD_RELOC_I960_CALLJ
1807 Reloc types used for i960/b.out.
1812 BFD_RELOC_SPARC_WDISP22
1818 BFD_RELOC_SPARC_GOT10
1820 BFD_RELOC_SPARC_GOT13
1822 BFD_RELOC_SPARC_GOT22
1824 BFD_RELOC_SPARC_PC10
1826 BFD_RELOC_SPARC_PC22
1828 BFD_RELOC_SPARC_WPLT30
1830 BFD_RELOC_SPARC_COPY
1832 BFD_RELOC_SPARC_GLOB_DAT
1834 BFD_RELOC_SPARC_JMP_SLOT
1836 BFD_RELOC_SPARC_RELATIVE
1838 BFD_RELOC_SPARC_UA32
1840 SPARC ELF relocations. There is probably some overlap with other
1841 relocation types already defined.
1844 BFD_RELOC_SPARC_BASE13
1846 BFD_RELOC_SPARC_BASE22
1848 I think these are specific to SPARC a.out (e.g., Sun 4).
1858 BFD_RELOC_SPARC_OLO10
1860 BFD_RELOC_SPARC_HH22
1862 BFD_RELOC_SPARC_HM10
1864 BFD_RELOC_SPARC_LM22
1866 BFD_RELOC_SPARC_PC_HH22
1868 BFD_RELOC_SPARC_PC_HM10
1870 BFD_RELOC_SPARC_PC_LM22
1872 BFD_RELOC_SPARC_WDISP16
1874 BFD_RELOC_SPARC_WDISP19
1882 BFD_RELOC_SPARC_DISP64
1885 BFD_RELOC_SPARC_PLT64
1887 BFD_RELOC_SPARC_HIX22
1889 BFD_RELOC_SPARC_LOX10
1897 BFD_RELOC_SPARC_REGISTER
1902 BFD_RELOC_SPARC_REV32
1904 SPARC little endian relocation
1907 BFD_RELOC_ALPHA_GPDISP_HI16
1909 Alpha ECOFF and ELF relocations. Some of these treat the symbol or
1910 "addend" in some special way.
1911 For GPDISP_HI16 ("gpdisp") relocations, the symbol is ignored when
1912 writing; when reading, it will be the absolute section symbol. The
1913 addend is the displacement in bytes of the "lda" instruction from
1914 the "ldah" instruction (which is at the address of this reloc).
1916 BFD_RELOC_ALPHA_GPDISP_LO16
1918 For GPDISP_LO16 ("ignore") relocations, the symbol is handled as
1919 with GPDISP_HI16 relocs. The addend is ignored when writing the
1920 relocations out, and is filled in with the file's GP value on
1921 reading, for convenience.
1924 BFD_RELOC_ALPHA_GPDISP
1926 The ELF GPDISP relocation is exactly the same as the GPDISP_HI16
1927 relocation except that there is no accompanying GPDISP_LO16
1931 BFD_RELOC_ALPHA_LITERAL
1933 BFD_RELOC_ALPHA_ELF_LITERAL
1935 BFD_RELOC_ALPHA_LITUSE
1937 The Alpha LITERAL/LITUSE relocs are produced by a symbol reference;
1938 the assembler turns it into a LDQ instruction to load the address of
1939 the symbol, and then fills in a register in the real instruction.
1941 The LITERAL reloc, at the LDQ instruction, refers to the .lita
1942 section symbol. The addend is ignored when writing, but is filled
1943 in with the file's GP value on reading, for convenience, as with the
1946 The ELF_LITERAL reloc is somewhere between 16_GOTOFF and GPDISP_LO16.
1947 It should refer to the symbol to be referenced, as with 16_GOTOFF,
1948 but it generates output not based on the position within the .got
1949 section, but relative to the GP value chosen for the file during the
1952 The LITUSE reloc, on the instruction using the loaded address, gives
1953 information to the linker that it might be able to use to optimize
1954 away some literal section references. The symbol is ignored (read
1955 as the absolute section symbol), and the "addend" indicates the type
1956 of instruction using the register:
1957 1 - "memory" fmt insn
1958 2 - byte-manipulation (byte offset reg)
1959 3 - jsr (target of branch)
1961 The GNU linker currently doesn't do any of this optimizing.
1964 BFD_RELOC_ALPHA_HINT
1966 The HINT relocation indicates a value that should be filled into the
1967 "hint" field of a jmp/jsr/ret instruction, for possible branch-
1968 prediction logic which may be provided on some processors.
1971 BFD_RELOC_ALPHA_LINKAGE
1973 The LINKAGE relocation outputs a linkage pair in the object file,
1974 which is filled by the linker.
1977 BFD_RELOC_ALPHA_CODEADDR
1979 The CODEADDR relocation outputs a STO_CA in the object file,
1980 which is filled by the linker.
1985 Bits 27..2 of the relocation address shifted right 2 bits;
1986 simple reloc otherwise.
1989 BFD_RELOC_MIPS16_JMP
1991 The MIPS16 jump instruction.
1994 BFD_RELOC_MIPS16_GPREL
1996 MIPS16 GP relative reloc.
2001 High 16 bits of 32-bit value; simple reloc.
2005 High 16 bits of 32-bit value but the low 16 bits will be sign
2006 extended and added to form the final result. If the low 16
2007 bits form a negative number, we need to add one to the high value
2008 to compensate for the borrow when the low bits are added.
2014 BFD_RELOC_PCREL_HI16_S
2016 Like BFD_RELOC_HI16_S, but PC relative.
2018 BFD_RELOC_PCREL_LO16
2020 Like BFD_RELOC_LO16, but PC relative.
2023 BFD_RELOC_MIPS_GPREL
2026 Relocation relative to the global pointer.
2029 BFD_RELOC_MIPS_LITERAL
2031 Relocation against a MIPS literal section.
2034 BFD_RELOC_MIPS_GOT16
2036 BFD_RELOC_MIPS_CALL16
2038 BFD_RELOC_MIPS_GPREL32
2041 BFD_RELOC_MIPS_GOT_HI16
2043 BFD_RELOC_MIPS_GOT_LO16
2045 BFD_RELOC_MIPS_CALL_HI16
2047 BFD_RELOC_MIPS_CALL_LO16
2051 BFD_RELOC_MIPS_GOT_PAGE
2053 BFD_RELOC_MIPS_GOT_OFST
2055 BFD_RELOC_MIPS_GOT_DISP
2058 MIPS ELF relocations.
2069 BFD_RELOC_386_GLOB_DAT
2071 BFD_RELOC_386_JUMP_SLOT
2073 BFD_RELOC_386_RELATIVE
2075 BFD_RELOC_386_GOTOFF
2079 i386/elf relocations
2082 BFD_RELOC_NS32K_IMM_8
2084 BFD_RELOC_NS32K_IMM_16
2086 BFD_RELOC_NS32K_IMM_32
2088 BFD_RELOC_NS32K_IMM_8_PCREL
2090 BFD_RELOC_NS32K_IMM_16_PCREL
2092 BFD_RELOC_NS32K_IMM_32_PCREL
2094 BFD_RELOC_NS32K_DISP_8
2096 BFD_RELOC_NS32K_DISP_16
2098 BFD_RELOC_NS32K_DISP_32
2100 BFD_RELOC_NS32K_DISP_8_PCREL
2102 BFD_RELOC_NS32K_DISP_16_PCREL
2104 BFD_RELOC_NS32K_DISP_32_PCREL
2109 BFD_RELOC_PJ_CODE_HI16
2111 BFD_RELOC_PJ_CODE_LO16
2113 BFD_RELOC_PJ_CODE_DIR16
2115 BFD_RELOC_PJ_CODE_DIR32
2117 BFD_RELOC_PJ_CODE_REL16
2119 BFD_RELOC_PJ_CODE_REL32
2121 Picojava relocs. Not all of these appear in object files.
2132 BFD_RELOC_PPC_B16_BRTAKEN
2134 BFD_RELOC_PPC_B16_BRNTAKEN
2138 BFD_RELOC_PPC_BA16_BRTAKEN
2140 BFD_RELOC_PPC_BA16_BRNTAKEN
2144 BFD_RELOC_PPC_GLOB_DAT
2146 BFD_RELOC_PPC_JMP_SLOT
2148 BFD_RELOC_PPC_RELATIVE
2150 BFD_RELOC_PPC_LOCAL24PC
2152 BFD_RELOC_PPC_EMB_NADDR32
2154 BFD_RELOC_PPC_EMB_NADDR16
2156 BFD_RELOC_PPC_EMB_NADDR16_LO
2158 BFD_RELOC_PPC_EMB_NADDR16_HI
2160 BFD_RELOC_PPC_EMB_NADDR16_HA
2162 BFD_RELOC_PPC_EMB_SDAI16
2164 BFD_RELOC_PPC_EMB_SDA2I16
2166 BFD_RELOC_PPC_EMB_SDA2REL
2168 BFD_RELOC_PPC_EMB_SDA21
2170 BFD_RELOC_PPC_EMB_MRKREF
2172 BFD_RELOC_PPC_EMB_RELSEC16
2174 BFD_RELOC_PPC_EMB_RELST_LO
2176 BFD_RELOC_PPC_EMB_RELST_HI
2178 BFD_RELOC_PPC_EMB_RELST_HA
2180 BFD_RELOC_PPC_EMB_BIT_FLD
2182 BFD_RELOC_PPC_EMB_RELSDA
2184 Power(rs6000) and PowerPC relocations.
2189 The type of reloc used to build a contructor table - at the moment
2190 probably a 32 bit wide absolute relocation, but the target can choose.
2191 It generally does map to one of the other relocation types.
2194 BFD_RELOC_ARM_PCREL_BRANCH
2196 ARM 26 bit pc-relative branch. The lowest two bits must be zero and are
2197 not stored in the instruction.
2199 BFD_RELOC_ARM_IMMEDIATE
2201 BFD_RELOC_ARM_ADRL_IMMEDIATE
2203 BFD_RELOC_ARM_OFFSET_IMM
2205 BFD_RELOC_ARM_SHIFT_IMM
2211 BFD_RELOC_ARM_CP_OFF_IMM
2213 BFD_RELOC_ARM_ADR_IMM
2215 BFD_RELOC_ARM_LDR_IMM
2217 BFD_RELOC_ARM_LITERAL
2219 BFD_RELOC_ARM_IN_POOL
2221 BFD_RELOC_ARM_OFFSET_IMM8
2223 BFD_RELOC_ARM_HWLITERAL
2225 BFD_RELOC_ARM_THUMB_ADD
2227 BFD_RELOC_ARM_THUMB_IMM
2229 BFD_RELOC_ARM_THUMB_SHIFT
2231 BFD_RELOC_ARM_THUMB_OFFSET
2237 BFD_RELOC_ARM_JUMP_SLOT
2241 BFD_RELOC_ARM_GLOB_DAT
2245 BFD_RELOC_ARM_RELATIVE
2247 BFD_RELOC_ARM_GOTOFF
2251 These relocs are only used within the ARM assembler. They are not
2252 (at present) written to any object files.
2255 BFD_RELOC_SH_PCDISP8BY2
2257 BFD_RELOC_SH_PCDISP12BY2
2261 BFD_RELOC_SH_IMM4BY2
2263 BFD_RELOC_SH_IMM4BY4
2267 BFD_RELOC_SH_IMM8BY2
2269 BFD_RELOC_SH_IMM8BY4
2271 BFD_RELOC_SH_PCRELIMM8BY2
2273 BFD_RELOC_SH_PCRELIMM8BY4
2275 BFD_RELOC_SH_SWITCH16
2277 BFD_RELOC_SH_SWITCH32
2291 Hitachi SH relocs. Not all of these appear in object files.
2294 BFD_RELOC_THUMB_PCREL_BRANCH9
2296 BFD_RELOC_THUMB_PCREL_BRANCH12
2298 BFD_RELOC_THUMB_PCREL_BRANCH23
2300 Thumb 23-, 12- and 9-bit pc-relative branches. The lowest bit must
2301 be zero and is not stored in the instruction.
2304 BFD_RELOC_ARC_B22_PCREL
2306 Argonaut RISC Core (ARC) relocs.
2307 ARC 22 bit pc-relative branch. The lowest two bits must be zero and are
2308 not stored in the instruction. The high 20 bits are installed in bits 26
2309 through 7 of the instruction.
2313 ARC 26 bit absolute branch. The lowest two bits must be zero and are not
2314 stored in the instruction. The high 24 bits are installed in bits 23
2318 BFD_RELOC_D10V_10_PCREL_R
2320 Mitsubishi D10V relocs.
2321 This is a 10-bit reloc with the right 2 bits
2324 BFD_RELOC_D10V_10_PCREL_L
2326 Mitsubishi D10V relocs.
2327 This is a 10-bit reloc with the right 2 bits
2328 assumed to be 0. This is the same as the previous reloc
2329 except it is in the left container, i.e.,
2330 shifted left 15 bits.
2334 This is an 18-bit reloc with the right 2 bits
2337 BFD_RELOC_D10V_18_PCREL
2339 This is an 18-bit reloc with the right 2 bits
2345 Mitsubishi D30V relocs.
2346 This is a 6-bit absolute reloc.
2348 BFD_RELOC_D30V_9_PCREL
2350 This is a 6-bit pc-relative reloc with
2351 the right 3 bits assumed to be 0.
2353 BFD_RELOC_D30V_9_PCREL_R
2355 This is a 6-bit pc-relative reloc with
2356 the right 3 bits assumed to be 0. Same
2357 as the previous reloc but on the right side
2362 This is a 12-bit absolute reloc with the
2363 right 3 bitsassumed to be 0.
2365 BFD_RELOC_D30V_15_PCREL
2367 This is a 12-bit pc-relative reloc with
2368 the right 3 bits assumed to be 0.
2370 BFD_RELOC_D30V_15_PCREL_R
2372 This is a 12-bit pc-relative reloc with
2373 the right 3 bits assumed to be 0. Same
2374 as the previous reloc but on the right side
2379 This is an 18-bit absolute reloc with
2380 the right 3 bits assumed to be 0.
2382 BFD_RELOC_D30V_21_PCREL
2384 This is an 18-bit pc-relative reloc with
2385 the right 3 bits assumed to be 0.
2387 BFD_RELOC_D30V_21_PCREL_R
2389 This is an 18-bit pc-relative reloc with
2390 the right 3 bits assumed to be 0. Same
2391 as the previous reloc but on the right side
2396 This is a 32-bit absolute reloc.
2398 BFD_RELOC_D30V_32_PCREL
2400 This is a 32-bit pc-relative reloc.
2405 Mitsubishi M32R relocs.
2406 This is a 24 bit absolute address.
2408 BFD_RELOC_M32R_10_PCREL
2410 This is a 10-bit pc-relative reloc with the right 2 bits assumed to be 0.
2412 BFD_RELOC_M32R_18_PCREL
2414 This is an 18-bit reloc with the right 2 bits assumed to be 0.
2416 BFD_RELOC_M32R_26_PCREL
2418 This is a 26-bit reloc with the right 2 bits assumed to be 0.
2420 BFD_RELOC_M32R_HI16_ULO
2422 This is a 16-bit reloc containing the high 16 bits of an address
2423 used when the lower 16 bits are treated as unsigned.
2425 BFD_RELOC_M32R_HI16_SLO
2427 This is a 16-bit reloc containing the high 16 bits of an address
2428 used when the lower 16 bits are treated as signed.
2432 This is a 16-bit reloc containing the lower 16 bits of an address.
2434 BFD_RELOC_M32R_SDA16
2436 This is a 16-bit reloc containing the small data area offset for use in
2437 add3, load, and store instructions.
2440 BFD_RELOC_V850_9_PCREL
2442 This is a 9-bit reloc
2444 BFD_RELOC_V850_22_PCREL
2446 This is a 22-bit reloc
2449 BFD_RELOC_V850_SDA_16_16_OFFSET
2451 This is a 16 bit offset from the short data area pointer.
2453 BFD_RELOC_V850_SDA_15_16_OFFSET
2455 This is a 16 bit offset (of which only 15 bits are used) from the
2456 short data area pointer.
2458 BFD_RELOC_V850_ZDA_16_16_OFFSET
2460 This is a 16 bit offset from the zero data area pointer.
2462 BFD_RELOC_V850_ZDA_15_16_OFFSET
2464 This is a 16 bit offset (of which only 15 bits are used) from the
2465 zero data area pointer.
2467 BFD_RELOC_V850_TDA_6_8_OFFSET
2469 This is an 8 bit offset (of which only 6 bits are used) from the
2470 tiny data area pointer.
2472 BFD_RELOC_V850_TDA_7_8_OFFSET
2474 This is an 8bit offset (of which only 7 bits are used) from the tiny
2477 BFD_RELOC_V850_TDA_7_7_OFFSET
2479 This is a 7 bit offset from the tiny data area pointer.
2481 BFD_RELOC_V850_TDA_16_16_OFFSET
2483 This is a 16 bit offset from the tiny data area pointer.
2486 BFD_RELOC_V850_TDA_4_5_OFFSET
2488 This is a 5 bit offset (of which only 4 bits are used) from the tiny
2491 BFD_RELOC_V850_TDA_4_4_OFFSET
2493 This is a 4 bit offset from the tiny data area pointer.
2495 BFD_RELOC_V850_SDA_16_16_SPLIT_OFFSET
2497 This is a 16 bit offset from the short data area pointer, with the
2498 bits placed non-contigously in the instruction.
2500 BFD_RELOC_V850_ZDA_16_16_SPLIT_OFFSET
2502 This is a 16 bit offset from the zero data area pointer, with the
2503 bits placed non-contigously in the instruction.
2505 BFD_RELOC_V850_CALLT_6_7_OFFSET
2507 This is a 6 bit offset from the call table base pointer.
2509 BFD_RELOC_V850_CALLT_16_16_OFFSET
2511 This is a 16 bit offset from the call table base pointer.
2515 BFD_RELOC_MN10300_32_PCREL
2517 This is a 32bit pcrel reloc for the mn10300, offset by two bytes in the
2520 BFD_RELOC_MN10300_16_PCREL
2522 This is a 16bit pcrel reloc for the mn10300, offset by two bytes in the
2528 This is a 8bit DP reloc for the tms320c30, where the most
2529 significant 8 bits of a 24 bit word are placed into the least
2530 significant 8 bits of the opcode.
2535 This is a 48 bit reloc for the FR30 that stores 32 bits.
2539 This is a 32 bit reloc for the FR30 that stores 20 bits split up into
2542 BFD_RELOC_FR30_6_IN_4
2544 This is a 16 bit reloc for the FR30 that stores a 6 bit word offset in
2547 BFD_RELOC_FR30_8_IN_8
2549 This is a 16 bit reloc for the FR30 that stores an 8 bit byte offset
2552 BFD_RELOC_FR30_9_IN_8
2554 This is a 16 bit reloc for the FR30 that stores a 9 bit short offset
2557 BFD_RELOC_FR30_10_IN_8
2559 This is a 16 bit reloc for the FR30 that stores a 10 bit word offset
2562 BFD_RELOC_FR30_9_PCREL
2564 This is a 16 bit reloc for the FR30 that stores a 9 bit pc relative
2565 short offset into 8 bits.
2567 BFD_RELOC_FR30_12_PCREL
2569 This is a 16 bit reloc for the FR30 that stores a 12 bit pc relative
2570 short offset into 11 bits.
2573 BFD_RELOC_MCORE_PCREL_IMM8BY4
2575 BFD_RELOC_MCORE_PCREL_IMM11BY2
2577 BFD_RELOC_MCORE_PCREL_IMM4BY2
2579 BFD_RELOC_MCORE_PCREL_32
2581 BFD_RELOC_MCORE_PCREL_JSR_IMM11BY2
2585 Motorola Mcore relocations.
2588 BFD_RELOC_VTABLE_INHERIT
2590 BFD_RELOC_VTABLE_ENTRY
2592 These two relocations are used by the linker to determine which of
2593 the entries in a C++ virtual function table are actually used. When
2594 the --gc-sections option is given, the linker will zero out the entries
2595 that are not used, so that the code for those functions need not be
2596 included in the output.
2598 VTABLE_INHERIT is a zero-space relocation used to describe to the
2599 linker the inheritence tree of a C++ virtual function table. The
2600 relocation's symbol should be the parent class' vtable, and the
2601 relocation should be located at the child vtable.
2603 VTABLE_ENTRY is a zero-space relocation that describes the use of a
2604 virtual function table entry. The reloc's symbol should refer to the
2605 table of the class mentioned in the code. Off of that base, an offset
2606 describes the entry that is being used. For Rela hosts, this offset
2607 is stored in the reloc's addend. For Rel hosts, we are forced to put
2608 this offset in the reloc's section offset.
2614 .typedef enum bfd_reloc_code_real bfd_reloc_code_real_type;
2620 bfd_reloc_type_lookup
2624 bfd_reloc_type_lookup (bfd *abfd, bfd_reloc_code_real_type code);
2627 Return a pointer to a howto structure which, when
2628 invoked, will perform the relocation @var{code} on data from the
2635 bfd_reloc_type_lookup (abfd, code)
2637 bfd_reloc_code_real_type code;
2639 return BFD_SEND (abfd, reloc_type_lookup, (abfd, code));
2642 static reloc_howto_type bfd_howto_32 =
2643 HOWTO (0, 00, 2, 32, false, 0, complain_overflow_bitfield, 0, "VRT32", false, 0xffffffff, 0xffffffff, true);
2648 bfd_default_reloc_type_lookup
2651 reloc_howto_type *bfd_default_reloc_type_lookup
2652 (bfd *abfd, bfd_reloc_code_real_type code);
2655 Provides a default relocation lookup routine for any architecture.
2661 bfd_default_reloc_type_lookup (abfd, code)
2663 bfd_reloc_code_real_type code;
2667 case BFD_RELOC_CTOR:
2668 /* The type of reloc used in a ctor, which will be as wide as the
2669 address - so either a 64, 32, or 16 bitter. */
2670 switch (bfd_get_arch_info (abfd)->bits_per_address)
2675 return &bfd_howto_32;
2684 return (reloc_howto_type *) NULL;
2689 bfd_get_reloc_code_name
2692 const char *bfd_get_reloc_code_name (bfd_reloc_code_real_type code);
2695 Provides a printable name for the supplied relocation code.
2696 Useful mainly for printing error messages.
2700 bfd_get_reloc_code_name (code)
2701 bfd_reloc_code_real_type code;
2703 if (code > BFD_RELOC_UNUSED)
2705 return bfd_reloc_code_real_names[(int)code];
2710 bfd_generic_relax_section
2713 boolean bfd_generic_relax_section
2716 struct bfd_link_info *,
2720 Provides default handling for relaxing for back ends which
2721 don't do relaxing -- i.e., does nothing.
2726 bfd_generic_relax_section (abfd, section, link_info, again)
2727 bfd *abfd ATTRIBUTE_UNUSED;
2728 asection *section ATTRIBUTE_UNUSED;
2729 struct bfd_link_info *link_info ATTRIBUTE_UNUSED;
2738 bfd_generic_gc_sections
2741 boolean bfd_generic_gc_sections
2742 (bfd *, struct bfd_link_info *);
2745 Provides default handling for relaxing for back ends which
2746 don't do section gc -- i.e., does nothing.
2751 bfd_generic_gc_sections (abfd, link_info)
2752 bfd *abfd ATTRIBUTE_UNUSED;
2753 struct bfd_link_info *link_info ATTRIBUTE_UNUSED;
2760 bfd_generic_get_relocated_section_contents
2764 bfd_generic_get_relocated_section_contents (bfd *abfd,
2765 struct bfd_link_info *link_info,
2766 struct bfd_link_order *link_order,
2768 boolean relocateable,
2772 Provides default handling of relocation effort for back ends
2773 which can't be bothered to do it efficiently.
2778 bfd_generic_get_relocated_section_contents (abfd, link_info, link_order, data,
2779 relocateable, symbols)
2781 struct bfd_link_info *link_info;
2782 struct bfd_link_order *link_order;
2784 boolean relocateable;
2787 /* Get enough memory to hold the stuff */
2788 bfd *input_bfd = link_order->u.indirect.section->owner;
2789 asection *input_section = link_order->u.indirect.section;
2791 long reloc_size = bfd_get_reloc_upper_bound (input_bfd, input_section);
2792 arelent **reloc_vector = NULL;
2798 reloc_vector = (arelent **) bfd_malloc ((size_t) reloc_size);
2799 if (reloc_vector == NULL && reloc_size != 0)
2802 /* read in the section */
2803 if (!bfd_get_section_contents (input_bfd,
2807 input_section->_raw_size))
2810 /* We're not relaxing the section, so just copy the size info */
2811 input_section->_cooked_size = input_section->_raw_size;
2812 input_section->reloc_done = true;
2814 reloc_count = bfd_canonicalize_reloc (input_bfd,
2818 if (reloc_count < 0)
2821 if (reloc_count > 0)
2824 for (parent = reloc_vector; *parent != (arelent *) NULL;
2827 char *error_message = (char *) NULL;
2828 bfd_reloc_status_type r =
2829 bfd_perform_relocation (input_bfd,
2833 relocateable ? abfd : (bfd *) NULL,
2838 asection *os = input_section->output_section;
2840 /* A partial link, so keep the relocs */
2841 os->orelocation[os->reloc_count] = *parent;
2845 if (r != bfd_reloc_ok)
2849 case bfd_reloc_undefined:
2850 if (!((*link_info->callbacks->undefined_symbol)
2851 (link_info, bfd_asymbol_name (*(*parent)->sym_ptr_ptr),
2852 input_bfd, input_section, (*parent)->address)))
2855 case bfd_reloc_dangerous:
2856 BFD_ASSERT (error_message != (char *) NULL);
2857 if (!((*link_info->callbacks->reloc_dangerous)
2858 (link_info, error_message, input_bfd, input_section,
2859 (*parent)->address)))
2862 case bfd_reloc_overflow:
2863 if (!((*link_info->callbacks->reloc_overflow)
2864 (link_info, bfd_asymbol_name (*(*parent)->sym_ptr_ptr),
2865 (*parent)->howto->name, (*parent)->addend,
2866 input_bfd, input_section, (*parent)->address)))
2869 case bfd_reloc_outofrange:
2878 if (reloc_vector != NULL)
2879 free (reloc_vector);
2883 if (reloc_vector != NULL)
2884 free (reloc_vector);