1 /* BFD support for handling relocation entries.
2 Copyright (C) 1990, 91, 92, 93, 94, 1995 Free Software Foundation, Inc.
3 Written by Cygnus Support.
5 This file is part of BFD, the Binary File Descriptor library.
7 This program is free software; you can redistribute it and/or modify
8 it under the terms of the GNU General Public License as published by
9 the Free Software Foundation; either version 2 of the License, or
10 (at your option) any later version.
12 This program is distributed in the hope that it will be useful,
13 but WITHOUT ANY WARRANTY; without even the implied warranty of
14 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
15 GNU General Public License for more details.
17 You should have received a copy of the GNU General Public License
18 along with this program; if not, write to the Free Software
19 Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. */
25 BFD maintains relocations in much the same way it maintains
26 symbols: they are left alone until required, then read in
27 en-mass and translated into an internal form. A common
28 routine <<bfd_perform_relocation>> acts upon the
29 canonical form to do the fixup.
31 Relocations are maintained on a per section basis,
32 while symbols are maintained on a per BFD basis.
34 All that a back end has to do to fit the BFD interface is to create
35 a <<struct reloc_cache_entry>> for each relocation
36 in a particular section, and fill in the right bits of the structures.
45 /* DO compile in the reloc_code name table from libbfd.h. */
46 #define _BFD_MAKE_TABLE_bfd_reloc_code_real
55 typedef arelent, howto manager, Relocations, Relocations
60 This is the structure of a relocation entry:
64 .typedef enum bfd_reloc_status
66 . {* No errors detected *}
69 . {* The relocation was performed, but there was an overflow. *}
72 . {* The address to relocate was not within the section supplied. *}
73 . bfd_reloc_outofrange,
75 . {* Used by special functions *}
78 . {* Unsupported relocation size requested. *}
79 . bfd_reloc_notsupported,
84 . {* The symbol to relocate against was undefined. *}
85 . bfd_reloc_undefined,
87 . {* The relocation was performed, but may not be ok - presently
88 . generated only when linking i960 coff files with i960 b.out
89 . symbols. If this type is returned, the error_message argument
90 . to bfd_perform_relocation will be set. *}
93 . bfd_reloc_status_type;
96 .typedef struct reloc_cache_entry
98 . {* A pointer into the canonical table of pointers *}
99 . struct symbol_cache_entry **sym_ptr_ptr;
101 . {* offset in section *}
102 . bfd_size_type address;
104 . {* addend for relocation value *}
107 . {* Pointer to how to perform the required relocation *}
108 . reloc_howto_type *howto;
117 Here is a description of each of the fields within an <<arelent>>:
121 The symbol table pointer points to a pointer to the symbol
122 associated with the relocation request. It is
123 the pointer into the table returned by the back end's
124 <<get_symtab>> action. @xref{Symbols}. The symbol is referenced
125 through a pointer to a pointer so that tools like the linker
126 can fix up all the symbols of the same name by modifying only
127 one pointer. The relocation routine looks in the symbol and
128 uses the base of the section the symbol is attached to and the
129 value of the symbol as the initial relocation offset. If the
130 symbol pointer is zero, then the section provided is looked up.
134 The <<address>> field gives the offset in bytes from the base of
135 the section data which owns the relocation record to the first
136 byte of relocatable information. The actual data relocated
137 will be relative to this point; for example, a relocation
138 type which modifies the bottom two bytes of a four byte word
139 would not touch the first byte pointed to in a big endian
144 The <<addend>> is a value provided by the back end to be added (!)
145 to the relocation offset. Its interpretation is dependent upon
146 the howto. For example, on the 68k the code:
152 | return foo[0x12345678];
155 Could be compiled into:
158 | moveb @@#12345678,d0
164 This could create a reloc pointing to <<foo>>, but leave the
165 offset in the data, something like:
168 |RELOCATION RECORDS FOR [.text]:
172 |00000000 4e56 fffc ; linkw fp,#-4
173 |00000004 1039 1234 5678 ; moveb @@#12345678,d0
174 |0000000a 49c0 ; extbl d0
175 |0000000c 4e5e ; unlk fp
179 Using coff and an 88k, some instructions don't have enough
180 space in them to represent the full address range, and
181 pointers have to be loaded in two parts. So you'd get something like:
184 | or.u r13,r0,hi16(_foo+0x12345678)
185 | ld.b r2,r13,lo16(_foo+0x12345678)
189 This should create two relocs, both pointing to <<_foo>>, and with
190 0x12340000 in their addend field. The data would consist of:
193 |RELOCATION RECORDS FOR [.text]:
195 |00000002 HVRT16 _foo+0x12340000
196 |00000006 LVRT16 _foo+0x12340000
198 |00000000 5da05678 ; or.u r13,r0,0x5678
199 |00000004 1c4d5678 ; ld.b r2,r13,0x5678
200 |00000008 f400c001 ; jmp r1
203 The relocation routine digs out the value from the data, adds
204 it to the addend to get the original offset, and then adds the
205 value of <<_foo>>. Note that all 32 bits have to be kept around
206 somewhere, to cope with carry from bit 15 to bit 16.
208 One further example is the sparc and the a.out format. The
209 sparc has a similar problem to the 88k, in that some
210 instructions don't have room for an entire offset, but on the
211 sparc the parts are created in odd sized lumps. The designers of
212 the a.out format chose to not use the data within the section
213 for storing part of the offset; all the offset is kept within
214 the reloc. Anything in the data should be ignored.
217 | sethi %hi(_foo+0x12345678),%g2
218 | ldsb [%g2+%lo(_foo+0x12345678)],%i0
222 Both relocs contain a pointer to <<foo>>, and the offsets
226 |RELOCATION RECORDS FOR [.text]:
228 |00000004 HI22 _foo+0x12345678
229 |00000008 LO10 _foo+0x12345678
231 |00000000 9de3bf90 ; save %sp,-112,%sp
232 |00000004 05000000 ; sethi %hi(_foo+0),%g2
233 |00000008 f048a000 ; ldsb [%g2+%lo(_foo+0)],%i0
234 |0000000c 81c7e008 ; ret
235 |00000010 81e80000 ; restore
240 The <<howto>> field can be imagined as a
241 relocation instruction. It is a pointer to a structure which
242 contains information on what to do with all of the other
243 information in the reloc record and data section. A back end
244 would normally have a relocation instruction set and turn
245 relocations into pointers to the correct structure on input -
246 but it would be possible to create each howto field on demand.
252 <<enum complain_overflow>>
254 Indicates what sort of overflow checking should be done when
255 performing a relocation.
259 .enum complain_overflow
261 . {* Do not complain on overflow. *}
262 . complain_overflow_dont,
264 . {* Complain if the bitfield overflows, whether it is considered
265 . as signed or unsigned. *}
266 . complain_overflow_bitfield,
268 . {* Complain if the value overflows when considered as signed
270 . complain_overflow_signed,
272 . {* Complain if the value overflows when considered as an
273 . unsigned number. *}
274 . complain_overflow_unsigned
283 The <<reloc_howto_type>> is a structure which contains all the
284 information that libbfd needs to know to tie up a back end's data.
287 .struct symbol_cache_entry; {* Forward declaration *}
289 .struct reloc_howto_struct
291 . {* The type field has mainly a documetary use - the back end can
292 . do what it wants with it, though normally the back end's
293 . external idea of what a reloc number is stored
294 . in this field. For example, a PC relative word relocation
295 . in a coff environment has the type 023 - because that's
296 . what the outside world calls a R_PCRWORD reloc. *}
299 . {* The value the final relocation is shifted right by. This drops
300 . unwanted data from the relocation. *}
301 . unsigned int rightshift;
303 . {* The size of the item to be relocated. This is *not* a
304 . power-of-two measure. To get the number of bytes operated
305 . on by a type of relocation, use bfd_get_reloc_size. *}
308 . {* The number of bits in the item to be relocated. This is used
309 . when doing overflow checking. *}
310 . unsigned int bitsize;
312 . {* Notes that the relocation is relative to the location in the
313 . data section of the addend. The relocation function will
314 . subtract from the relocation value the address of the location
315 . being relocated. *}
316 . boolean pc_relative;
318 . {* The bit position of the reloc value in the destination.
319 . The relocated value is left shifted by this amount. *}
320 . unsigned int bitpos;
322 . {* What type of overflow error should be checked for when
324 . enum complain_overflow complain_on_overflow;
326 . {* If this field is non null, then the supplied function is
327 . called rather than the normal function. This allows really
328 . strange relocation methods to be accomodated (e.g., i960 callj
330 . bfd_reloc_status_type (*special_function)
331 . PARAMS ((bfd *abfd,
332 . arelent *reloc_entry,
333 . struct symbol_cache_entry *symbol,
335 . asection *input_section,
337 . char **error_message));
339 . {* The textual name of the relocation type. *}
342 . {* When performing a partial link, some formats must modify the
343 . relocations rather than the data - this flag signals this.*}
344 . boolean partial_inplace;
346 . {* The src_mask selects which parts of the read in data
347 . are to be used in the relocation sum. E.g., if this was an 8 bit
348 . bit of data which we read and relocated, this would be
349 . 0x000000ff. When we have relocs which have an addend, such as
350 . sun4 extended relocs, the value in the offset part of a
351 . relocating field is garbage so we never use it. In this case
352 . the mask would be 0x00000000. *}
355 . {* The dst_mask selects which parts of the instruction are replaced
356 . into the instruction. In most cases src_mask == dst_mask,
357 . except in the above special case, where dst_mask would be
358 . 0x000000ff, and src_mask would be 0x00000000. *}
361 . {* When some formats create PC relative instructions, they leave
362 . the value of the pc of the place being relocated in the offset
363 . slot of the instruction, so that a PC relative relocation can
364 . be made just by adding in an ordinary offset (e.g., sun3 a.out).
365 . Some formats leave the displacement part of an instruction
366 . empty (e.g., m88k bcs); this flag signals the fact.*}
367 . boolean pcrel_offset;
378 The HOWTO define is horrible and will go away.
381 .#define HOWTO(C, R,S,B, P, BI, O, SF, NAME, INPLACE, MASKSRC, MASKDST, PC) \
382 . {(unsigned)C,R,S,B, P, BI, O,SF,NAME,INPLACE,MASKSRC,MASKDST,PC}
385 And will be replaced with the totally magic way. But for the
386 moment, we are compatible, so do it this way.
389 .#define NEWHOWTO( FUNCTION, NAME,SIZE,REL,IN) HOWTO(0,0,SIZE,0,REL,0,complain_overflow_dont,FUNCTION, NAME,false,0,0,IN)
392 Helper routine to turn a symbol into a relocation value.
394 .#define HOWTO_PREPARE(relocation, symbol) \
396 . if (symbol != (asymbol *)NULL) { \
397 . if (bfd_is_com_section (symbol->section)) { \
401 . relocation = symbol->value; \
413 int bfd_get_reloc_size (reloc_howto_type *);
416 For a reloc_howto_type that operates on a fixed number of bytes,
417 this returns the number of bytes operated on.
421 bfd_get_reloc_size (howto)
422 reloc_howto_type *howto;
443 How relocs are tied together in an <<asection>>:
445 .typedef struct relent_chain {
447 . struct relent_chain *next;
456 bfd_perform_relocation
459 bfd_reloc_status_type
460 bfd_perform_relocation
462 arelent *reloc_entry,
464 asection *input_section,
466 char **error_message);
469 If @var{output_bfd} is supplied to this function, the
470 generated image will be relocatable; the relocations are
471 copied to the output file after they have been changed to
472 reflect the new state of the world. There are two ways of
473 reflecting the results of partial linkage in an output file:
474 by modifying the output data in place, and by modifying the
475 relocation record. Some native formats (e.g., basic a.out and
476 basic coff) have no way of specifying an addend in the
477 relocation type, so the addend has to go in the output data.
478 This is no big deal since in these formats the output data
479 slot will always be big enough for the addend. Complex reloc
480 types with addends were invented to solve just this problem.
481 The @var{error_message} argument is set to an error message if
482 this return @code{bfd_reloc_dangerous}.
487 bfd_reloc_status_type
488 bfd_perform_relocation (abfd, reloc_entry, data, input_section, output_bfd,
491 arelent *reloc_entry;
493 asection *input_section;
495 char **error_message;
498 bfd_reloc_status_type flag = bfd_reloc_ok;
499 bfd_size_type addr = reloc_entry->address;
500 bfd_vma output_base = 0;
501 reloc_howto_type *howto = reloc_entry->howto;
502 asection *reloc_target_output_section;
505 symbol = *(reloc_entry->sym_ptr_ptr);
506 if (bfd_is_abs_section (symbol->section)
507 && output_bfd != (bfd *) NULL)
509 reloc_entry->address += input_section->output_offset;
513 /* If we are not producing relocateable output, return an error if
514 the symbol is not defined. An undefined weak symbol is
515 considered to have a value of zero (SVR4 ABI, p. 4-27). */
516 if (bfd_is_und_section (symbol->section)
517 && (symbol->flags & BSF_WEAK) == 0
518 && output_bfd == (bfd *) NULL)
519 flag = bfd_reloc_undefined;
521 /* If there is a function supplied to handle this relocation type,
522 call it. It'll return `bfd_reloc_continue' if further processing
524 if (howto->special_function)
526 bfd_reloc_status_type cont;
527 cont = howto->special_function (abfd, reloc_entry, symbol, data,
528 input_section, output_bfd,
530 if (cont != bfd_reloc_continue)
534 /* Is the address of the relocation really within the section? */
535 if (reloc_entry->address > input_section->_cooked_size)
536 return bfd_reloc_outofrange;
538 /* Work out which section the relocation is targetted at and the
539 initial relocation command value. */
541 /* Get symbol value. (Common symbols are special.) */
542 if (bfd_is_com_section (symbol->section))
545 relocation = symbol->value;
548 reloc_target_output_section = symbol->section->output_section;
550 /* Convert input-section-relative symbol value to absolute. */
551 if (output_bfd && howto->partial_inplace == false)
554 output_base = reloc_target_output_section->vma;
556 relocation += output_base + symbol->section->output_offset;
558 /* Add in supplied addend. */
559 relocation += reloc_entry->addend;
561 /* Here the variable relocation holds the final address of the
562 symbol we are relocating against, plus any addend. */
564 if (howto->pc_relative == true)
566 /* This is a PC relative relocation. We want to set RELOCATION
567 to the distance between the address of the symbol and the
568 location. RELOCATION is already the address of the symbol.
570 We start by subtracting the address of the section containing
573 If pcrel_offset is set, we must further subtract the position
574 of the location within the section. Some targets arrange for
575 the addend to be the negative of the position of the location
576 within the section; for example, i386-aout does this. For
577 i386-aout, pcrel_offset is false. Some other targets do not
578 include the position of the location; for example, m88kbcs,
579 or ELF. For those targets, pcrel_offset is true.
581 If we are producing relocateable output, then we must ensure
582 that this reloc will be correctly computed when the final
583 relocation is done. If pcrel_offset is false we want to wind
584 up with the negative of the location within the section,
585 which means we must adjust the existing addend by the change
586 in the location within the section. If pcrel_offset is true
587 we do not want to adjust the existing addend at all.
589 FIXME: This seems logical to me, but for the case of
590 producing relocateable output it is not what the code
591 actually does. I don't want to change it, because it seems
592 far too likely that something will break. */
595 input_section->output_section->vma + input_section->output_offset;
597 if (howto->pcrel_offset == true)
598 relocation -= reloc_entry->address;
601 if (output_bfd != (bfd *) NULL)
603 if (howto->partial_inplace == false)
605 /* This is a partial relocation, and we want to apply the relocation
606 to the reloc entry rather than the raw data. Modify the reloc
607 inplace to reflect what we now know. */
608 reloc_entry->addend = relocation;
609 reloc_entry->address += input_section->output_offset;
614 /* This is a partial relocation, but inplace, so modify the
617 If we've relocated with a symbol with a section, change
618 into a ref to the section belonging to the symbol. */
620 reloc_entry->address += input_section->output_offset;
623 if (abfd->xvec->flavour == bfd_target_coff_flavour
624 && strcmp (abfd->xvec->name, "aixcoff-rs6000") != 0
625 && strcmp (abfd->xvec->name, "xcoff-powermac") != 0
626 && strcmp (abfd->xvec->name, "coff-Intel-little") != 0
627 && strcmp (abfd->xvec->name, "coff-Intel-big") != 0)
630 /* For m68k-coff, the addend was being subtracted twice during
631 relocation with -r. Removing the line below this comment
632 fixes that problem; see PR 2953.
634 However, Ian wrote the following, regarding removing the line below,
635 which explains why it is still enabled: --djm
637 If you put a patch like that into BFD you need to check all the COFF
638 linkers. I am fairly certain that patch will break coff-i386 (e.g.,
639 SCO); see coff_i386_reloc in coff-i386.c where I worked around the
640 problem in a different way. There may very well be a reason that the
641 code works as it does.
643 Hmmm. The first obvious point is that bfd_perform_relocation should
644 not have any tests that depend upon the flavour. It's seem like
645 entirely the wrong place for such a thing. The second obvious point
646 is that the current code ignores the reloc addend when producing
647 relocateable output for COFF. That's peculiar. In fact, I really
648 have no idea what the point of the line you want to remove is.
650 A typical COFF reloc subtracts the old value of the symbol and adds in
651 the new value to the location in the object file (if it's a pc
652 relative reloc it adds the difference between the symbol value and the
653 location). When relocating we need to preserve that property.
655 BFD handles this by setting the addend to the negative of the old
656 value of the symbol. Unfortunately it handles common symbols in a
657 non-standard way (it doesn't subtract the old value) but that's a
658 different story (we can't change it without losing backward
659 compatibility with old object files) (coff-i386 does subtract the old
660 value, to be compatible with existing coff-i386 targets, like SCO).
662 So everything works fine when not producing relocateable output. When
663 we are producing relocateable output, logically we should do exactly
664 what we do when not producing relocateable output. Therefore, your
665 patch is correct. In fact, it should probably always just set
666 reloc_entry->addend to 0 for all cases, since it is, in fact, going to
667 add the value into the object file. This won't hurt the COFF code,
668 which doesn't use the addend; I'm not sure what it will do to other
669 formats (the thing to check for would be whether any formats both use
670 the addend and set partial_inplace).
672 When I wanted to make coff-i386 produce relocateable output, I ran
673 into the problem that you are running into: I wanted to remove that
674 line. Rather than risk it, I made the coff-i386 relocs use a special
675 function; it's coff_i386_reloc in coff-i386.c. The function
676 specifically adds the addend field into the object file, knowing that
677 bfd_perform_relocation is not going to. If you remove that line, then
678 coff-i386.c will wind up adding the addend field in twice. It's
679 trivial to fix; it just needs to be done.
681 The problem with removing the line is just that it may break some
682 working code. With BFD it's hard to be sure of anything. The right
683 way to deal with this is simply to build and test at least all the
684 supported COFF targets. It should be straightforward if time and disk
685 space consuming. For each target:
687 2) generate some executable, and link it using -r (I would
688 probably use paranoia.o and link against newlib/libc.a, which
689 for all the supported targets would be available in
690 /usr/cygnus/progressive/H-host/target/lib/libc.a).
691 3) make the change to reloc.c
692 4) rebuild the linker
694 6) if the resulting object files are the same, you have at least
696 7) if they are different you have to figure out which version is
699 relocation -= reloc_entry->addend;
701 reloc_entry->addend = 0;
705 reloc_entry->addend = relocation;
711 reloc_entry->addend = 0;
714 /* FIXME: This overflow checking is incomplete, because the value
715 might have overflowed before we get here. For a correct check we
716 need to compute the value in a size larger than bitsize, but we
717 can't reasonably do that for a reloc the same size as a host
719 FIXME: We should also do overflow checking on the result after
720 adding in the value contained in the object file. */
721 if (howto->complain_on_overflow != complain_overflow_dont
722 && flag == bfd_reloc_ok)
726 /* Get the value that will be used for the relocation, but
727 starting at bit position zero. */
728 check = relocation >> howto->rightshift;
729 switch (howto->complain_on_overflow)
731 case complain_overflow_signed:
733 /* Assumes two's complement. */
734 bfd_signed_vma reloc_signed_max = (1 << (howto->bitsize - 1)) - 1;
735 bfd_signed_vma reloc_signed_min = ~reloc_signed_max;
737 /* The above right shift is incorrect for a signed value.
738 Fix it up by forcing on the upper bits. */
739 if (howto->rightshift > 0
740 && (bfd_signed_vma) relocation < 0)
741 check |= ((bfd_vma) - 1
743 >> howto->rightshift));
744 if ((bfd_signed_vma) check > reloc_signed_max
745 || (bfd_signed_vma) check < reloc_signed_min)
746 flag = bfd_reloc_overflow;
749 case complain_overflow_unsigned:
751 /* Assumes two's complement. This expression avoids
752 overflow if howto->bitsize is the number of bits in
754 bfd_vma reloc_unsigned_max =
755 (((1 << (howto->bitsize - 1)) - 1) << 1) | 1;
757 if ((bfd_vma) check > reloc_unsigned_max)
758 flag = bfd_reloc_overflow;
761 case complain_overflow_bitfield:
763 /* Assumes two's complement. This expression avoids
764 overflow if howto->bitsize is the number of bits in
766 bfd_vma reloc_bits = (((1 << (howto->bitsize - 1)) - 1) << 1) | 1;
768 if (((bfd_vma) check & ~reloc_bits) != 0
769 && ((bfd_vma) check & ~reloc_bits) != (-1 & ~reloc_bits))
771 /* The above right shift is incorrect for a signed
772 value. See if turning on the upper bits fixes the
774 if (howto->rightshift > 0
775 && (bfd_signed_vma) relocation < 0)
777 check |= ((bfd_vma) - 1
779 >> howto->rightshift));
780 if (((bfd_vma) check & ~reloc_bits) != (-1 & ~reloc_bits))
781 flag = bfd_reloc_overflow;
784 flag = bfd_reloc_overflow;
794 Either we are relocating all the way, or we don't want to apply
795 the relocation to the reloc entry (probably because there isn't
796 any room in the output format to describe addends to relocs)
799 /* The cast to bfd_vma avoids a bug in the Alpha OSF/1 C compiler
800 (OSF version 1.3, compiler version 3.11). It miscompiles the
814 x <<= (unsigned long) s.i0;
818 printf ("succeeded (%lx)\n", x);
822 relocation >>= (bfd_vma) howto->rightshift;
824 /* Shift everything up to where it's going to be used */
826 relocation <<= (bfd_vma) howto->bitpos;
828 /* Wait for the day when all have the mask in them */
831 i instruction to be left alone
832 o offset within instruction
833 r relocation offset to apply
842 i i i i i o o o o o from bfd_get<size>
843 and S S S S S to get the size offset we want
844 + r r r r r r r r r r to get the final value to place
845 and D D D D D to chop to right size
846 -----------------------
849 ... i i i i i o o o o o from bfd_get<size>
850 and N N N N N get instruction
851 -----------------------
857 -----------------------
858 R R R R R R R R R R put into bfd_put<size>
862 x = ( (x & ~howto->dst_mask) | (((x & howto->src_mask) + relocation) & howto->dst_mask))
868 char x = bfd_get_8 (abfd, (char *) data + addr);
870 bfd_put_8 (abfd, x, (unsigned char *) data + addr);
877 short x = bfd_get_16 (abfd, (bfd_byte *) data + addr);
879 bfd_put_16 (abfd, x, (unsigned char *) data + addr);
885 long x = bfd_get_32 (abfd, (bfd_byte *) data + addr);
887 bfd_put_32 (abfd, x, (bfd_byte *) data + addr);
892 long x = bfd_get_32 (abfd, (bfd_byte *) data + addr);
893 relocation = -relocation;
895 bfd_put_32 (abfd, x, (bfd_byte *) data + addr);
901 long x = bfd_get_16 (abfd, (bfd_byte *) data + addr);
902 relocation = -relocation;
904 bfd_put_16 (abfd, x, (bfd_byte *) data + addr);
916 bfd_vma x = bfd_get_64 (abfd, (bfd_byte *) data + addr);
918 bfd_put_64 (abfd, x, (bfd_byte *) data + addr);
925 return bfd_reloc_other;
933 bfd_install_relocation
936 bfd_reloc_status_type
937 bfd_install_relocation
939 arelent *reloc_entry,
940 PTR data, bfd_vma data_start,
941 asection *input_section,
942 char **error_message);
945 This looks remarkably like <<bfd_perform_relocation>>, except it
946 does not expect that the section contents have been filled in.
947 I.e., it's suitable for use when creating, rather than applying
950 For now, this function should be considered reserved for the
956 bfd_reloc_status_type
957 bfd_install_relocation (abfd, reloc_entry, data_start, data_start_offset,
958 input_section, error_message)
960 arelent *reloc_entry;
962 bfd_vma data_start_offset;
963 asection *input_section;
964 char **error_message;
967 bfd_reloc_status_type flag = bfd_reloc_ok;
968 bfd_size_type addr = reloc_entry->address;
969 bfd_vma output_base = 0;
970 reloc_howto_type *howto = reloc_entry->howto;
971 asection *reloc_target_output_section;
975 symbol = *(reloc_entry->sym_ptr_ptr);
976 if (bfd_is_abs_section (symbol->section))
978 reloc_entry->address += input_section->output_offset;
982 /* If there is a function supplied to handle this relocation type,
983 call it. It'll return `bfd_reloc_continue' if further processing
985 if (howto->special_function)
987 bfd_reloc_status_type cont;
988 /* XXX - The special_function calls haven't been fixed up to deal
989 with creating new relocations and section contents. */
990 cont = howto->special_function (abfd, reloc_entry, symbol,
991 /* XXX - Non-portable! */
992 ((bfd_byte *) data_start
993 - data_start_offset),
994 input_section, abfd, error_message);
995 if (cont != bfd_reloc_continue)
999 /* Is the address of the relocation really within the section? */
1000 if (reloc_entry->address > input_section->_cooked_size)
1001 return bfd_reloc_outofrange;
1003 /* Work out which section the relocation is targetted at and the
1004 initial relocation command value. */
1006 /* Get symbol value. (Common symbols are special.) */
1007 if (bfd_is_com_section (symbol->section))
1010 relocation = symbol->value;
1013 reloc_target_output_section = symbol->section->output_section;
1015 /* Convert input-section-relative symbol value to absolute. */
1016 if (howto->partial_inplace == false)
1019 output_base = reloc_target_output_section->vma;
1021 relocation += output_base + symbol->section->output_offset;
1023 /* Add in supplied addend. */
1024 relocation += reloc_entry->addend;
1026 /* Here the variable relocation holds the final address of the
1027 symbol we are relocating against, plus any addend. */
1029 if (howto->pc_relative == true)
1031 /* This is a PC relative relocation. We want to set RELOCATION
1032 to the distance between the address of the symbol and the
1033 location. RELOCATION is already the address of the symbol.
1035 We start by subtracting the address of the section containing
1038 If pcrel_offset is set, we must further subtract the position
1039 of the location within the section. Some targets arrange for
1040 the addend to be the negative of the position of the location
1041 within the section; for example, i386-aout does this. For
1042 i386-aout, pcrel_offset is false. Some other targets do not
1043 include the position of the location; for example, m88kbcs,
1044 or ELF. For those targets, pcrel_offset is true.
1046 If we are producing relocateable output, then we must ensure
1047 that this reloc will be correctly computed when the final
1048 relocation is done. If pcrel_offset is false we want to wind
1049 up with the negative of the location within the section,
1050 which means we must adjust the existing addend by the change
1051 in the location within the section. If pcrel_offset is true
1052 we do not want to adjust the existing addend at all.
1054 FIXME: This seems logical to me, but for the case of
1055 producing relocateable output it is not what the code
1056 actually does. I don't want to change it, because it seems
1057 far too likely that something will break. */
1060 input_section->output_section->vma + input_section->output_offset;
1062 if (howto->pcrel_offset == true && howto->partial_inplace == true)
1063 relocation -= reloc_entry->address;
1066 if (howto->partial_inplace == false)
1068 /* This is a partial relocation, and we want to apply the relocation
1069 to the reloc entry rather than the raw data. Modify the reloc
1070 inplace to reflect what we now know. */
1071 reloc_entry->addend = relocation;
1072 reloc_entry->address += input_section->output_offset;
1077 /* This is a partial relocation, but inplace, so modify the
1080 If we've relocated with a symbol with a section, change
1081 into a ref to the section belonging to the symbol. */
1083 reloc_entry->address += input_section->output_offset;
1086 if (abfd->xvec->flavour == bfd_target_coff_flavour
1087 && strcmp (abfd->xvec->name, "aixcoff-rs6000") != 0
1088 && strcmp (abfd->xvec->name, "xcoff-powermac") != 0
1089 && strcmp (abfd->xvec->name, "coff-Intel-little") != 0
1090 && strcmp (abfd->xvec->name, "coff-Intel-big") != 0)
1093 /* For m68k-coff, the addend was being subtracted twice during
1094 relocation with -r. Removing the line below this comment
1095 fixes that problem; see PR 2953.
1097 However, Ian wrote the following, regarding removing the line below,
1098 which explains why it is still enabled: --djm
1100 If you put a patch like that into BFD you need to check all the COFF
1101 linkers. I am fairly certain that patch will break coff-i386 (e.g.,
1102 SCO); see coff_i386_reloc in coff-i386.c where I worked around the
1103 problem in a different way. There may very well be a reason that the
1104 code works as it does.
1106 Hmmm. The first obvious point is that bfd_install_relocation should
1107 not have any tests that depend upon the flavour. It's seem like
1108 entirely the wrong place for such a thing. The second obvious point
1109 is that the current code ignores the reloc addend when producing
1110 relocateable output for COFF. That's peculiar. In fact, I really
1111 have no idea what the point of the line you want to remove is.
1113 A typical COFF reloc subtracts the old value of the symbol and adds in
1114 the new value to the location in the object file (if it's a pc
1115 relative reloc it adds the difference between the symbol value and the
1116 location). When relocating we need to preserve that property.
1118 BFD handles this by setting the addend to the negative of the old
1119 value of the symbol. Unfortunately it handles common symbols in a
1120 non-standard way (it doesn't subtract the old value) but that's a
1121 different story (we can't change it without losing backward
1122 compatibility with old object files) (coff-i386 does subtract the old
1123 value, to be compatible with existing coff-i386 targets, like SCO).
1125 So everything works fine when not producing relocateable output. When
1126 we are producing relocateable output, logically we should do exactly
1127 what we do when not producing relocateable output. Therefore, your
1128 patch is correct. In fact, it should probably always just set
1129 reloc_entry->addend to 0 for all cases, since it is, in fact, going to
1130 add the value into the object file. This won't hurt the COFF code,
1131 which doesn't use the addend; I'm not sure what it will do to other
1132 formats (the thing to check for would be whether any formats both use
1133 the addend and set partial_inplace).
1135 When I wanted to make coff-i386 produce relocateable output, I ran
1136 into the problem that you are running into: I wanted to remove that
1137 line. Rather than risk it, I made the coff-i386 relocs use a special
1138 function; it's coff_i386_reloc in coff-i386.c. The function
1139 specifically adds the addend field into the object file, knowing that
1140 bfd_install_relocation is not going to. If you remove that line, then
1141 coff-i386.c will wind up adding the addend field in twice. It's
1142 trivial to fix; it just needs to be done.
1144 The problem with removing the line is just that it may break some
1145 working code. With BFD it's hard to be sure of anything. The right
1146 way to deal with this is simply to build and test at least all the
1147 supported COFF targets. It should be straightforward if time and disk
1148 space consuming. For each target:
1150 2) generate some executable, and link it using -r (I would
1151 probably use paranoia.o and link against newlib/libc.a, which
1152 for all the supported targets would be available in
1153 /usr/cygnus/progressive/H-host/target/lib/libc.a).
1154 3) make the change to reloc.c
1155 4) rebuild the linker
1157 6) if the resulting object files are the same, you have at least
1159 7) if they are different you have to figure out which version is
1162 relocation -= reloc_entry->addend;
1164 reloc_entry->addend = 0;
1168 reloc_entry->addend = relocation;
1172 /* FIXME: This overflow checking is incomplete, because the value
1173 might have overflowed before we get here. For a correct check we
1174 need to compute the value in a size larger than bitsize, but we
1175 can't reasonably do that for a reloc the same size as a host
1178 FIXME: We should also do overflow checking on the result after
1179 adding in the value contained in the object file. */
1180 if (howto->complain_on_overflow != complain_overflow_dont)
1184 /* Get the value that will be used for the relocation, but
1185 starting at bit position zero. */
1186 check = relocation >> howto->rightshift;
1187 switch (howto->complain_on_overflow)
1189 case complain_overflow_signed:
1191 /* Assumes two's complement. */
1192 bfd_signed_vma reloc_signed_max = (1 << (howto->bitsize - 1)) - 1;
1193 bfd_signed_vma reloc_signed_min = ~reloc_signed_max;
1195 /* The above right shift is incorrect for a signed value.
1196 Fix it up by forcing on the upper bits. */
1197 if (howto->rightshift > 0
1198 && (bfd_signed_vma) relocation < 0)
1199 check |= ((bfd_vma) - 1
1201 >> howto->rightshift));
1202 if ((bfd_signed_vma) check > reloc_signed_max
1203 || (bfd_signed_vma) check < reloc_signed_min)
1204 flag = bfd_reloc_overflow;
1207 case complain_overflow_unsigned:
1209 /* Assumes two's complement. This expression avoids
1210 overflow if howto->bitsize is the number of bits in
1212 bfd_vma reloc_unsigned_max =
1213 (((1 << (howto->bitsize - 1)) - 1) << 1) | 1;
1215 if ((bfd_vma) check > reloc_unsigned_max)
1216 flag = bfd_reloc_overflow;
1219 case complain_overflow_bitfield:
1221 /* Assumes two's complement. This expression avoids
1222 overflow if howto->bitsize is the number of bits in
1224 bfd_vma reloc_bits = (((1 << (howto->bitsize - 1)) - 1) << 1) | 1;
1226 if (((bfd_vma) check & ~reloc_bits) != 0
1227 && ((bfd_vma) check & ~reloc_bits) != (-1 & ~reloc_bits))
1229 /* The above right shift is incorrect for a signed
1230 value. See if turning on the upper bits fixes the
1232 if (howto->rightshift > 0
1233 && (bfd_signed_vma) relocation < 0)
1235 check |= ((bfd_vma) - 1
1237 >> howto->rightshift));
1238 if (((bfd_vma) check & ~reloc_bits) != (-1 & ~reloc_bits))
1239 flag = bfd_reloc_overflow;
1242 flag = bfd_reloc_overflow;
1252 Either we are relocating all the way, or we don't want to apply
1253 the relocation to the reloc entry (probably because there isn't
1254 any room in the output format to describe addends to relocs)
1257 /* The cast to bfd_vma avoids a bug in the Alpha OSF/1 C compiler
1258 (OSF version 1.3, compiler version 3.11). It miscompiles the
1272 x <<= (unsigned long) s.i0;
1274 printf ("failed\n");
1276 printf ("succeeded (%lx)\n", x);
1280 relocation >>= (bfd_vma) howto->rightshift;
1282 /* Shift everything up to where it's going to be used */
1284 relocation <<= (bfd_vma) howto->bitpos;
1286 /* Wait for the day when all have the mask in them */
1289 i instruction to be left alone
1290 o offset within instruction
1291 r relocation offset to apply
1300 i i i i i o o o o o from bfd_get<size>
1301 and S S S S S to get the size offset we want
1302 + r r r r r r r r r r to get the final value to place
1303 and D D D D D to chop to right size
1304 -----------------------
1307 ... i i i i i o o o o o from bfd_get<size>
1308 and N N N N N get instruction
1309 -----------------------
1315 -----------------------
1316 R R R R R R R R R R put into bfd_put<size>
1320 x = ( (x & ~howto->dst_mask) | (((x & howto->src_mask) + relocation) & howto->dst_mask))
1322 data = (bfd_byte *) data_start + (addr - data_start_offset);
1324 switch (howto->size)
1328 char x = bfd_get_8 (abfd, (char *) data);
1330 bfd_put_8 (abfd, x, (unsigned char *) data);
1337 short x = bfd_get_16 (abfd, (bfd_byte *) data);
1339 bfd_put_16 (abfd, x, (unsigned char *) data);
1345 long x = bfd_get_32 (abfd, (bfd_byte *) data);
1347 bfd_put_32 (abfd, x, (bfd_byte *) data);
1352 long x = bfd_get_32 (abfd, (bfd_byte *) data);
1353 relocation = -relocation;
1355 bfd_put_32 (abfd, x, (bfd_byte *) data);
1366 bfd_vma x = bfd_get_64 (abfd, (bfd_byte *) data);
1368 bfd_put_64 (abfd, x, (bfd_byte *) data);
1372 return bfd_reloc_other;
1378 /* This relocation routine is used by some of the backend linkers.
1379 They do not construct asymbol or arelent structures, so there is no
1380 reason for them to use bfd_perform_relocation. Also,
1381 bfd_perform_relocation is so hacked up it is easier to write a new
1382 function than to try to deal with it.
1384 This routine does a final relocation. It should not be used when
1385 generating relocateable output.
1387 FIXME: This routine ignores any special_function in the HOWTO,
1388 since the existing special_function values have been written for
1389 bfd_perform_relocation.
1391 HOWTO is the reloc howto information.
1392 INPUT_BFD is the BFD which the reloc applies to.
1393 INPUT_SECTION is the section which the reloc applies to.
1394 CONTENTS is the contents of the section.
1395 ADDRESS is the address of the reloc within INPUT_SECTION.
1396 VALUE is the value of the symbol the reloc refers to.
1397 ADDEND is the addend of the reloc. */
1399 bfd_reloc_status_type
1400 _bfd_final_link_relocate (howto, input_bfd, input_section, contents, address,
1402 reloc_howto_type *howto;
1404 asection *input_section;
1412 /* Sanity check the address. */
1413 if (address > input_section->_raw_size)
1414 return bfd_reloc_outofrange;
1416 /* This function assumes that we are dealing with a basic relocation
1417 against a symbol. We want to compute the value of the symbol to
1418 relocate to. This is just VALUE, the value of the symbol, plus
1419 ADDEND, any addend associated with the reloc. */
1420 relocation = value + addend;
1422 /* If the relocation is PC relative, we want to set RELOCATION to
1423 the distance between the symbol (currently in RELOCATION) and the
1424 location we are relocating. Some targets (e.g., i386-aout)
1425 arrange for the contents of the section to be the negative of the
1426 offset of the location within the section; for such targets
1427 pcrel_offset is false. Other targets (e.g., m88kbcs or ELF)
1428 simply leave the contents of the section as zero; for such
1429 targets pcrel_offset is true. If pcrel_offset is false we do not
1430 need to subtract out the offset of the location within the
1431 section (which is just ADDRESS). */
1432 if (howto->pc_relative)
1434 relocation -= (input_section->output_section->vma
1435 + input_section->output_offset);
1436 if (howto->pcrel_offset)
1437 relocation -= address;
1440 return _bfd_relocate_contents (howto, input_bfd, relocation,
1441 contents + address);
1444 /* Relocate a given location using a given value and howto. */
1446 bfd_reloc_status_type
1447 _bfd_relocate_contents (howto, input_bfd, relocation, location)
1448 reloc_howto_type *howto;
1457 /* If the size is negative, negate RELOCATION. This isn't very
1459 if (howto->size < 0)
1460 relocation = -relocation;
1462 /* Get the value we are going to relocate. */
1463 size = bfd_get_reloc_size (howto);
1470 x = bfd_get_8 (input_bfd, location);
1473 x = bfd_get_16 (input_bfd, location);
1476 x = bfd_get_32 (input_bfd, location);
1480 x = bfd_get_64 (input_bfd, location);
1487 /* Check for overflow. FIXME: We may drop bits during the addition
1488 which we don't check for. We must either check at every single
1489 operation, which would be tedious, or we must do the computations
1490 in a type larger than bfd_vma, which would be inefficient. */
1492 if (howto->complain_on_overflow != complain_overflow_dont)
1495 bfd_signed_vma signed_check;
1497 bfd_signed_vma signed_add;
1499 if (howto->rightshift == 0)
1502 signed_check = (bfd_signed_vma) relocation;
1506 /* Drop unwanted bits from the value we are relocating to. */
1507 check = relocation >> howto->rightshift;
1509 /* If this is a signed value, the rightshift just dropped
1510 leading 1 bits (assuming twos complement). */
1511 if ((bfd_signed_vma) relocation >= 0)
1512 signed_check = check;
1514 signed_check = (check
1516 & ~((bfd_vma) - 1 >> howto->rightshift)));
1519 /* Get the value from the object file. */
1520 add = x & howto->src_mask;
1522 /* Get the value from the object file with an appropriate sign.
1523 The expression involving howto->src_mask isolates the upper
1524 bit of src_mask. If that bit is set in the value we are
1525 adding, it is negative, and we subtract out that number times
1526 two. If src_mask includes the highest possible bit, then we
1527 can not get the upper bit, but that does not matter since
1528 signed_add needs no adjustment to become negative in that
1531 if ((add & (((~howto->src_mask) >> 1) & howto->src_mask)) != 0)
1532 signed_add -= (((~howto->src_mask) >> 1) & howto->src_mask) << 1;
1534 /* Add the value from the object file, shifted so that it is a
1536 if (howto->bitpos == 0)
1539 signed_check += signed_add;
1543 check += add >> howto->bitpos;
1545 /* For the signed case we use ADD, rather than SIGNED_ADD,
1546 to avoid warnings from SVR4 cc. This is OK since we
1547 explictly handle the sign bits. */
1548 if (signed_add >= 0)
1549 signed_check += add >> howto->bitpos;
1551 signed_check += ((add >> howto->bitpos)
1553 & ~((bfd_vma) - 1 >> howto->bitpos)));
1556 switch (howto->complain_on_overflow)
1558 case complain_overflow_signed:
1560 /* Assumes two's complement. */
1561 bfd_signed_vma reloc_signed_max = (1 << (howto->bitsize - 1)) - 1;
1562 bfd_signed_vma reloc_signed_min = ~reloc_signed_max;
1564 if (signed_check > reloc_signed_max
1565 || signed_check < reloc_signed_min)
1569 case complain_overflow_unsigned:
1571 /* Assumes two's complement. This expression avoids
1572 overflow if howto->bitsize is the number of bits in
1574 bfd_vma reloc_unsigned_max =
1575 (((1 << (howto->bitsize - 1)) - 1) << 1) | 1;
1577 if (check > reloc_unsigned_max)
1581 case complain_overflow_bitfield:
1583 /* Assumes two's complement. This expression avoids
1584 overflow if howto->bitsize is the number of bits in
1586 bfd_vma reloc_bits = (((1 << (howto->bitsize - 1)) - 1) << 1) | 1;
1588 if ((check & ~reloc_bits) != 0
1589 && (((bfd_vma) signed_check & ~reloc_bits)
1590 != (-1 & ~reloc_bits)))
1599 /* Put RELOCATION in the right bits. */
1600 relocation >>= (bfd_vma) howto->rightshift;
1601 relocation <<= (bfd_vma) howto->bitpos;
1603 /* Add RELOCATION to the right bits of X. */
1604 x = ((x & ~howto->dst_mask)
1605 | (((x & howto->src_mask) + relocation) & howto->dst_mask));
1607 /* Put the relocated value back in the object file. */
1614 bfd_put_8 (input_bfd, x, location);
1617 bfd_put_16 (input_bfd, x, location);
1620 bfd_put_32 (input_bfd, x, location);
1624 bfd_put_64 (input_bfd, x, location);
1631 return overflow ? bfd_reloc_overflow : bfd_reloc_ok;
1637 howto manager, , typedef arelent, Relocations
1642 When an application wants to create a relocation, but doesn't
1643 know what the target machine might call it, it can find out by
1644 using this bit of code.
1653 The insides of a reloc code. The idea is that, eventually, there
1654 will be one enumerator for every type of relocation we ever do.
1655 Pass one of these values to <<bfd_reloc_type_lookup>>, and it'll
1656 return a howto pointer.
1658 This does mean that the application must determine the correct
1659 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
1876 BFD_RELOC_SPARC_GLOB_JMP
1884 Some relocations we're using for SPARC V9 -- subject to change.
1887 BFD_RELOC_ALPHA_GPDISP_HI16
1889 Alpha ECOFF and ELF relocations. Some of these treat the symbol or
1890 "addend" in some special way.
1891 For GPDISP_HI16 ("gpdisp") relocations, the symbol is ignored when
1892 writing; when reading, it will be the absolute section symbol. The
1893 addend is the displacement in bytes of the "lda" instruction from
1894 the "ldah" instruction (which is at the address of this reloc).
1896 BFD_RELOC_ALPHA_GPDISP_LO16
1898 For GPDISP_LO16 ("ignore") relocations, the symbol is handled as
1899 with GPDISP_HI16 relocs. The addend is ignored when writing the
1900 relocations out, and is filled in with the file's GP value on
1901 reading, for convenience.
1904 BFD_RELOC_ALPHA_GPDISP
1906 The ELF GPDISP relocation is exactly the same as the GPDISP_HI16
1907 relocation except that there is no accompanying GPDISP_LO16
1911 BFD_RELOC_ALPHA_LITERAL
1913 BFD_RELOC_ALPHA_LITUSE
1915 The Alpha LITERAL/LITUSE relocs are produced by a symbol reference;
1916 the assembler turns it into a LDQ instruction to load the address of
1917 the symbol, and then fills in a register in the real instruction.
1919 The LITERAL reloc, at the LDQ instruction, refers to the .lita
1920 section symbol. The addend is ignored when writing, but is filled
1921 in with the file's GP value on reading, for convenience, as with the
1924 The LITUSE reloc, on the instruction using the loaded address, gives
1925 information to the linker that it might be able to use to optimize
1926 away some literal section references. The symbol is ignored (read
1927 as the absolute section symbol), and the "addend" indicates the type
1928 of instruction using the register:
1929 1 - "memory" fmt insn
1930 2 - byte-manipulation (byte offset reg)
1931 3 - jsr (target of branch)
1933 The GNU linker currently doesn't do any of this optimizing.
1936 BFD_RELOC_ALPHA_HINT
1938 The HINT relocation indicates a value that should be filled into the
1939 "hint" field of a jmp/jsr/ret instruction, for possible branch-
1940 prediction logic which may be provided on some processors.
1943 BFD_RELOC_ALPHA_LINKAGE
1945 The LINKAGE relocation outputs a linkage pair in the object file,
1946 which is filled by the linker.
1951 Bits 27..2 of the relocation address shifted right 2 bits;
1952 simple reloc otherwise.
1957 High 16 bits of 32-bit value; simple reloc.
1961 High 16 bits of 32-bit value but the low 16 bits will be sign
1962 extended and added to form the final result. If the low 16
1963 bits form a negative number, we need to add one to the high value
1964 to compensate for the borrow when the low bits are added.
1970 BFD_RELOC_PCREL_HI16_S
1972 Like BFD_RELOC_HI16_S, but PC relative.
1974 BFD_RELOC_PCREL_LO16
1976 Like BFD_RELOC_LO16, but PC relative.
1979 BFD_RELOC_MIPS_GPREL
1982 Relocation relative to the global pointer.
1985 BFD_RELOC_MIPS_LITERAL
1987 Relocation against a MIPS literal section.
1990 BFD_RELOC_MIPS_GOT16
1992 BFD_RELOC_MIPS_CALL16
1994 BFD_RELOC_MIPS_GPREL32
1997 BFD_RELOC_MIPS_GOT_HI16
1999 BFD_RELOC_MIPS_GOT_LO16
2001 BFD_RELOC_MIPS_CALL_HI16
2003 BFD_RELOC_MIPS_CALL_LO16
2005 MIPS ELF relocations.
2014 BFD_RELOC_386_GLOB_DAT
2016 BFD_RELOC_386_JUMP_SLOT
2018 BFD_RELOC_386_RELATIVE
2020 BFD_RELOC_386_GOTOFF
2024 i386/elf relocations
2027 BFD_RELOC_NS32K_IMM_8
2029 BFD_RELOC_NS32K_IMM_16
2031 BFD_RELOC_NS32K_IMM_32
2033 BFD_RELOC_NS32K_IMM_8_PCREL
2035 BFD_RELOC_NS32K_IMM_16_PCREL
2037 BFD_RELOC_NS32K_IMM_32_PCREL
2039 BFD_RELOC_NS32K_DISP_8
2041 BFD_RELOC_NS32K_DISP_16
2043 BFD_RELOC_NS32K_DISP_32
2045 BFD_RELOC_NS32K_DISP_8_PCREL
2047 BFD_RELOC_NS32K_DISP_16_PCREL
2049 BFD_RELOC_NS32K_DISP_32_PCREL
2062 BFD_RELOC_PPC_B16_BRTAKEN
2064 BFD_RELOC_PPC_B16_BRNTAKEN
2068 BFD_RELOC_PPC_BA16_BRTAKEN
2070 BFD_RELOC_PPC_BA16_BRNTAKEN
2074 BFD_RELOC_PPC_GLOB_DAT
2076 BFD_RELOC_PPC_JMP_SLOT
2078 BFD_RELOC_PPC_RELATIVE
2080 BFD_RELOC_PPC_LOCAL24PC
2082 BFD_RELOC_PPC_EMB_NADDR32
2084 BFD_RELOC_PPC_EMB_NADDR16
2086 BFD_RELOC_PPC_EMB_NADDR16_LO
2088 BFD_RELOC_PPC_EMB_NADDR16_HI
2090 BFD_RELOC_PPC_EMB_NADDR16_HA
2092 BFD_RELOC_PPC_EMB_SDAI16
2094 BFD_RELOC_PPC_EMB_SDA2I16
2096 BFD_RELOC_PPC_EMB_SDA2REL
2098 BFD_RELOC_PPC_EMB_SDA21
2100 BFD_RELOC_PPC_EMB_MRKREF
2102 BFD_RELOC_PPC_EMB_RELSEC16
2104 BFD_RELOC_PPC_EMB_RELST_LO
2106 BFD_RELOC_PPC_EMB_RELST_HI
2108 BFD_RELOC_PPC_EMB_RELST_HA
2110 BFD_RELOC_PPC_EMB_BIT_FLD
2112 BFD_RELOC_PPC_EMB_RELSDA
2114 Power(rs6000) and PowerPC relocations.
2119 The type of reloc used to build a contructor table - at the moment
2120 probably a 32 bit wide absolute relocation, but the target can choose.
2121 It generally does map to one of the other relocation types.
2124 BFD_RELOC_ARM_PCREL_BRANCH
2126 ARM 26 bit pc-relative branch. The lowest two bits must be zero and are
2127 not stored in the instruction.
2129 BFD_RELOC_ARM_IMMEDIATE
2131 BFD_RELOC_ARM_OFFSET_IMM
2133 BFD_RELOC_ARM_SHIFT_IMM
2139 BFD_RELOC_ARM_CP_OFF_IMM
2141 BFD_RELOC_ARM_ADR_IMM
2143 BFD_RELOC_ARM_LDR_IMM
2145 BFD_RELOC_ARM_LITERAL
2147 BFD_RELOC_ARM_IN_POOL
2149 BFD_RELOC_ARM_OFFSET_IMM8
2151 BFD_RELOC_ARM_HWLITERAL
2153 These relocs are only used within the ARM assembler. They are not
2154 (at present) written to any object files.
2157 {* start-sanitize-arc *}
2159 BFD_RELOC_ARC_B22_PCREL
2161 Argonaut RISC Core (ARC) relocs.
2162 ARC 22 bit pc-relative branch. The lowest two bits must be zero and are
2163 not stored in the instruction. The high 20 bits are installed in bits 26
2164 through 7 of the instruction.
2168 ARC 26 bit absolute branch. The lowest two bits must be zero and are not
2169 stored in the instruction. The high 24 bits are installed in bits 23
2172 {* end-sanitize-arc *}
2175 {* start-sanitize-d10v *}
2177 BFD_RELOC_D10V_10_PCREL_R
2179 Mitsubishi D10V relocs.
2180 This is a 10-bit reloc with the right 2 bits
2183 BFD_RELOC_D10V_10_PCREL_L
2185 Mitsubishi D10V relocs.
2186 This is a 10-bit reloc with the right 2 bits
2187 assumed to be 0. This is the same as the previous reloc
2188 except it is in the left container, i.e.,
2189 shifted left 15 bits.
2193 This is an 18-bit reloc with the right 2 bits
2196 BFD_RELOC_D10V_18_PCREL
2198 This is an 18-bit reloc with the right 2 bits
2201 {* end-sanitize-d10v *}
2207 .typedef enum bfd_reloc_code_real bfd_reloc_code_real_type;
2213 bfd_reloc_type_lookup
2217 bfd_reloc_type_lookup (bfd *abfd, bfd_reloc_code_real_type code);
2220 Return a pointer to a howto structure which, when
2221 invoked, will perform the relocation @var{code} on data from the
2228 bfd_reloc_type_lookup (abfd, code)
2230 bfd_reloc_code_real_type code;
2232 return BFD_SEND (abfd, reloc_type_lookup, (abfd, code));
2235 static reloc_howto_type bfd_howto_32 =
2236 HOWTO (0, 00, 2, 32, false, 0, complain_overflow_bitfield, 0, "VRT32", false, 0xffffffff, 0xffffffff, true);
2241 bfd_default_reloc_type_lookup
2244 reloc_howto_type *bfd_default_reloc_type_lookup
2245 (bfd *abfd, bfd_reloc_code_real_type code);
2248 Provides a default relocation lookup routine for any architecture.
2254 bfd_default_reloc_type_lookup (abfd, code)
2256 bfd_reloc_code_real_type code;
2260 case BFD_RELOC_CTOR:
2261 /* The type of reloc used in a ctor, which will be as wide as the
2262 address - so either a 64, 32, or 16 bitter. */
2263 switch (bfd_get_arch_info (abfd)->bits_per_address)
2268 return &bfd_howto_32;
2277 return (reloc_howto_type *) NULL;
2282 bfd_get_reloc_code_name
2285 const char *bfd_get_reloc_code_name (bfd_reloc_code_real_type code);
2288 Provides a printable name for the supplied relocation code.
2289 Useful mainly for printing error messages.
2293 bfd_get_reloc_code_name (code)
2294 bfd_reloc_code_real_type code;
2296 if (code > BFD_RELOC_UNUSED)
2298 return bfd_reloc_code_real_names[(int)code];
2303 bfd_generic_relax_section
2306 boolean bfd_generic_relax_section
2309 struct bfd_link_info *,
2313 Provides default handling for relaxing for back ends which
2314 don't do relaxing -- i.e., does nothing.
2319 bfd_generic_relax_section (abfd, section, link_info, again)
2322 struct bfd_link_info *link_info;
2331 bfd_generic_get_relocated_section_contents
2335 bfd_generic_get_relocated_section_contents (bfd *abfd,
2336 struct bfd_link_info *link_info,
2337 struct bfd_link_order *link_order,
2339 boolean relocateable,
2343 Provides default handling of relocation effort for back ends
2344 which can't be bothered to do it efficiently.
2349 bfd_generic_get_relocated_section_contents (abfd, link_info, link_order, data,
2350 relocateable, symbols)
2352 struct bfd_link_info *link_info;
2353 struct bfd_link_order *link_order;
2355 boolean relocateable;
2358 /* Get enough memory to hold the stuff */
2359 bfd *input_bfd = link_order->u.indirect.section->owner;
2360 asection *input_section = link_order->u.indirect.section;
2362 long reloc_size = bfd_get_reloc_upper_bound (input_bfd, input_section);
2363 arelent **reloc_vector = NULL;
2369 reloc_vector = (arelent **) bfd_malloc ((size_t) reloc_size);
2370 if (reloc_vector == NULL && reloc_size != 0)
2373 /* read in the section */
2374 if (!bfd_get_section_contents (input_bfd,
2378 input_section->_raw_size))
2381 /* We're not relaxing the section, so just copy the size info */
2382 input_section->_cooked_size = input_section->_raw_size;
2383 input_section->reloc_done = true;
2385 reloc_count = bfd_canonicalize_reloc (input_bfd,
2389 if (reloc_count < 0)
2392 if (reloc_count > 0)
2395 for (parent = reloc_vector; *parent != (arelent *) NULL;
2398 char *error_message = (char *) NULL;
2399 bfd_reloc_status_type r =
2400 bfd_perform_relocation (input_bfd,
2404 relocateable ? abfd : (bfd *) NULL,
2409 asection *os = input_section->output_section;
2411 /* A partial link, so keep the relocs */
2412 os->orelocation[os->reloc_count] = *parent;
2416 if (r != bfd_reloc_ok)
2420 case bfd_reloc_undefined:
2421 if (!((*link_info->callbacks->undefined_symbol)
2422 (link_info, bfd_asymbol_name (*(*parent)->sym_ptr_ptr),
2423 input_bfd, input_section, (*parent)->address)))
2426 case bfd_reloc_dangerous:
2427 BFD_ASSERT (error_message != (char *) NULL);
2428 if (!((*link_info->callbacks->reloc_dangerous)
2429 (link_info, error_message, input_bfd, input_section,
2430 (*parent)->address)))
2433 case bfd_reloc_overflow:
2434 if (!((*link_info->callbacks->reloc_overflow)
2435 (link_info, bfd_asymbol_name (*(*parent)->sym_ptr_ptr),
2436 (*parent)->howto->name, (*parent)->addend,
2437 input_bfd, input_section, (*parent)->address)))
2440 case bfd_reloc_outofrange:
2449 if (reloc_vector != NULL)
2450 free (reloc_vector);
2454 if (reloc_vector != NULL)
2455 free (reloc_vector);