1 /* BFD support for handling relocation entries.
2 Copyright (C) 1990, 91, 92, 93, 94, 95, 1996 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);
876 short x = bfd_get_16 (abfd, (bfd_byte *) data + addr);
878 bfd_put_16 (abfd, x, (unsigned char *) data + addr);
883 long x = bfd_get_32 (abfd, (bfd_byte *) data + addr);
885 bfd_put_32 (abfd, x, (bfd_byte *) data + addr);
890 long x = bfd_get_32 (abfd, (bfd_byte *) data + addr);
891 relocation = -relocation;
893 bfd_put_32 (abfd, x, (bfd_byte *) data + addr);
899 long x = bfd_get_16 (abfd, (bfd_byte *) data + addr);
900 relocation = -relocation;
902 bfd_put_16 (abfd, x, (bfd_byte *) data + addr);
913 bfd_vma x = bfd_get_64 (abfd, (bfd_byte *) data + addr);
915 bfd_put_64 (abfd, x, (bfd_byte *) data + addr);
922 return bfd_reloc_other;
930 bfd_install_relocation
933 bfd_reloc_status_type
934 bfd_install_relocation
936 arelent *reloc_entry,
937 PTR data, bfd_vma data_start,
938 asection *input_section,
939 char **error_message);
942 This looks remarkably like <<bfd_perform_relocation>>, except it
943 does not expect that the section contents have been filled in.
944 I.e., it's suitable for use when creating, rather than applying
947 For now, this function should be considered reserved for the
953 bfd_reloc_status_type
954 bfd_install_relocation (abfd, reloc_entry, data_start, data_start_offset,
955 input_section, error_message)
957 arelent *reloc_entry;
959 bfd_vma data_start_offset;
960 asection *input_section;
961 char **error_message;
964 bfd_reloc_status_type flag = bfd_reloc_ok;
965 bfd_size_type addr = reloc_entry->address;
966 bfd_vma output_base = 0;
967 reloc_howto_type *howto = reloc_entry->howto;
968 asection *reloc_target_output_section;
972 symbol = *(reloc_entry->sym_ptr_ptr);
973 if (bfd_is_abs_section (symbol->section))
975 reloc_entry->address += input_section->output_offset;
979 /* If there is a function supplied to handle this relocation type,
980 call it. It'll return `bfd_reloc_continue' if further processing
982 if (howto->special_function)
984 bfd_reloc_status_type cont;
985 /* XXX - The special_function calls haven't been fixed up to deal
986 with creating new relocations and section contents. */
987 cont = howto->special_function (abfd, reloc_entry, symbol,
988 /* XXX - Non-portable! */
989 ((bfd_byte *) data_start
990 - data_start_offset),
991 input_section, abfd, error_message);
992 if (cont != bfd_reloc_continue)
996 /* Is the address of the relocation really within the section? */
997 if (reloc_entry->address > input_section->_cooked_size)
998 return bfd_reloc_outofrange;
1000 /* Work out which section the relocation is targetted at and the
1001 initial relocation command value. */
1003 /* Get symbol value. (Common symbols are special.) */
1004 if (bfd_is_com_section (symbol->section))
1007 relocation = symbol->value;
1010 reloc_target_output_section = symbol->section->output_section;
1012 /* Convert input-section-relative symbol value to absolute. */
1013 if (howto->partial_inplace == false)
1016 output_base = reloc_target_output_section->vma;
1018 relocation += output_base + symbol->section->output_offset;
1020 /* Add in supplied addend. */
1021 relocation += reloc_entry->addend;
1023 /* Here the variable relocation holds the final address of the
1024 symbol we are relocating against, plus any addend. */
1026 if (howto->pc_relative == true)
1028 /* This is a PC relative relocation. We want to set RELOCATION
1029 to the distance between the address of the symbol and the
1030 location. RELOCATION is already the address of the symbol.
1032 We start by subtracting the address of the section containing
1035 If pcrel_offset is set, we must further subtract the position
1036 of the location within the section. Some targets arrange for
1037 the addend to be the negative of the position of the location
1038 within the section; for example, i386-aout does this. For
1039 i386-aout, pcrel_offset is false. Some other targets do not
1040 include the position of the location; for example, m88kbcs,
1041 or ELF. For those targets, pcrel_offset is true.
1043 If we are producing relocateable output, then we must ensure
1044 that this reloc will be correctly computed when the final
1045 relocation is done. If pcrel_offset is false we want to wind
1046 up with the negative of the location within the section,
1047 which means we must adjust the existing addend by the change
1048 in the location within the section. If pcrel_offset is true
1049 we do not want to adjust the existing addend at all.
1051 FIXME: This seems logical to me, but for the case of
1052 producing relocateable output it is not what the code
1053 actually does. I don't want to change it, because it seems
1054 far too likely that something will break. */
1057 input_section->output_section->vma + input_section->output_offset;
1059 if (howto->pcrel_offset == true && howto->partial_inplace == true)
1060 relocation -= reloc_entry->address;
1063 if (howto->partial_inplace == false)
1065 /* This is a partial relocation, and we want to apply the relocation
1066 to the reloc entry rather than the raw data. Modify the reloc
1067 inplace to reflect what we now know. */
1068 reloc_entry->addend = relocation;
1069 reloc_entry->address += input_section->output_offset;
1074 /* This is a partial relocation, but inplace, so modify the
1077 If we've relocated with a symbol with a section, change
1078 into a ref to the section belonging to the symbol. */
1080 reloc_entry->address += input_section->output_offset;
1083 if (abfd->xvec->flavour == bfd_target_coff_flavour
1084 && strcmp (abfd->xvec->name, "aixcoff-rs6000") != 0
1085 && strcmp (abfd->xvec->name, "xcoff-powermac") != 0
1086 && strcmp (abfd->xvec->name, "coff-Intel-little") != 0
1087 && strcmp (abfd->xvec->name, "coff-Intel-big") != 0)
1090 /* For m68k-coff, the addend was being subtracted twice during
1091 relocation with -r. Removing the line below this comment
1092 fixes that problem; see PR 2953.
1094 However, Ian wrote the following, regarding removing the line below,
1095 which explains why it is still enabled: --djm
1097 If you put a patch like that into BFD you need to check all the COFF
1098 linkers. I am fairly certain that patch will break coff-i386 (e.g.,
1099 SCO); see coff_i386_reloc in coff-i386.c where I worked around the
1100 problem in a different way. There may very well be a reason that the
1101 code works as it does.
1103 Hmmm. The first obvious point is that bfd_install_relocation should
1104 not have any tests that depend upon the flavour. It's seem like
1105 entirely the wrong place for such a thing. The second obvious point
1106 is that the current code ignores the reloc addend when producing
1107 relocateable output for COFF. That's peculiar. In fact, I really
1108 have no idea what the point of the line you want to remove is.
1110 A typical COFF reloc subtracts the old value of the symbol and adds in
1111 the new value to the location in the object file (if it's a pc
1112 relative reloc it adds the difference between the symbol value and the
1113 location). When relocating we need to preserve that property.
1115 BFD handles this by setting the addend to the negative of the old
1116 value of the symbol. Unfortunately it handles common symbols in a
1117 non-standard way (it doesn't subtract the old value) but that's a
1118 different story (we can't change it without losing backward
1119 compatibility with old object files) (coff-i386 does subtract the old
1120 value, to be compatible with existing coff-i386 targets, like SCO).
1122 So everything works fine when not producing relocateable output. When
1123 we are producing relocateable output, logically we should do exactly
1124 what we do when not producing relocateable output. Therefore, your
1125 patch is correct. In fact, it should probably always just set
1126 reloc_entry->addend to 0 for all cases, since it is, in fact, going to
1127 add the value into the object file. This won't hurt the COFF code,
1128 which doesn't use the addend; I'm not sure what it will do to other
1129 formats (the thing to check for would be whether any formats both use
1130 the addend and set partial_inplace).
1132 When I wanted to make coff-i386 produce relocateable output, I ran
1133 into the problem that you are running into: I wanted to remove that
1134 line. Rather than risk it, I made the coff-i386 relocs use a special
1135 function; it's coff_i386_reloc in coff-i386.c. The function
1136 specifically adds the addend field into the object file, knowing that
1137 bfd_install_relocation is not going to. If you remove that line, then
1138 coff-i386.c will wind up adding the addend field in twice. It's
1139 trivial to fix; it just needs to be done.
1141 The problem with removing the line is just that it may break some
1142 working code. With BFD it's hard to be sure of anything. The right
1143 way to deal with this is simply to build and test at least all the
1144 supported COFF targets. It should be straightforward if time and disk
1145 space consuming. For each target:
1147 2) generate some executable, and link it using -r (I would
1148 probably use paranoia.o and link against newlib/libc.a, which
1149 for all the supported targets would be available in
1150 /usr/cygnus/progressive/H-host/target/lib/libc.a).
1151 3) make the change to reloc.c
1152 4) rebuild the linker
1154 6) if the resulting object files are the same, you have at least
1156 7) if they are different you have to figure out which version is
1159 relocation -= reloc_entry->addend;
1161 reloc_entry->addend = 0;
1165 reloc_entry->addend = relocation;
1169 /* FIXME: This overflow checking is incomplete, because the value
1170 might have overflowed before we get here. For a correct check we
1171 need to compute the value in a size larger than bitsize, but we
1172 can't reasonably do that for a reloc the same size as a host
1175 FIXME: We should also do overflow checking on the result after
1176 adding in the value contained in the object file. */
1177 if (howto->complain_on_overflow != complain_overflow_dont)
1181 /* Get the value that will be used for the relocation, but
1182 starting at bit position zero. */
1183 check = relocation >> howto->rightshift;
1184 switch (howto->complain_on_overflow)
1186 case complain_overflow_signed:
1188 /* Assumes two's complement. */
1189 bfd_signed_vma reloc_signed_max = (1 << (howto->bitsize - 1)) - 1;
1190 bfd_signed_vma reloc_signed_min = ~reloc_signed_max;
1192 /* The above right shift is incorrect for a signed value.
1193 Fix it up by forcing on the upper bits. */
1194 if (howto->rightshift > 0
1195 && (bfd_signed_vma) relocation < 0)
1196 check |= ((bfd_vma) - 1
1198 >> howto->rightshift));
1199 if ((bfd_signed_vma) check > reloc_signed_max
1200 || (bfd_signed_vma) check < reloc_signed_min)
1201 flag = bfd_reloc_overflow;
1204 case complain_overflow_unsigned:
1206 /* Assumes two's complement. This expression avoids
1207 overflow if howto->bitsize is the number of bits in
1209 bfd_vma reloc_unsigned_max =
1210 (((1 << (howto->bitsize - 1)) - 1) << 1) | 1;
1212 if ((bfd_vma) check > reloc_unsigned_max)
1213 flag = bfd_reloc_overflow;
1216 case complain_overflow_bitfield:
1218 /* Assumes two's complement. This expression avoids
1219 overflow if howto->bitsize is the number of bits in
1221 bfd_vma reloc_bits = (((1 << (howto->bitsize - 1)) - 1) << 1) | 1;
1223 if (((bfd_vma) check & ~reloc_bits) != 0
1224 && ((bfd_vma) check & ~reloc_bits) != (-1 & ~reloc_bits))
1226 /* The above right shift is incorrect for a signed
1227 value. See if turning on the upper bits fixes the
1229 if (howto->rightshift > 0
1230 && (bfd_signed_vma) relocation < 0)
1232 check |= ((bfd_vma) - 1
1234 >> howto->rightshift));
1235 if (((bfd_vma) check & ~reloc_bits) != (-1 & ~reloc_bits))
1236 flag = bfd_reloc_overflow;
1239 flag = bfd_reloc_overflow;
1249 Either we are relocating all the way, or we don't want to apply
1250 the relocation to the reloc entry (probably because there isn't
1251 any room in the output format to describe addends to relocs)
1254 /* The cast to bfd_vma avoids a bug in the Alpha OSF/1 C compiler
1255 (OSF version 1.3, compiler version 3.11). It miscompiles the
1269 x <<= (unsigned long) s.i0;
1271 printf ("failed\n");
1273 printf ("succeeded (%lx)\n", x);
1277 relocation >>= (bfd_vma) howto->rightshift;
1279 /* Shift everything up to where it's going to be used */
1281 relocation <<= (bfd_vma) howto->bitpos;
1283 /* Wait for the day when all have the mask in them */
1286 i instruction to be left alone
1287 o offset within instruction
1288 r relocation offset to apply
1297 i i i i i o o o o o from bfd_get<size>
1298 and S S S S S to get the size offset we want
1299 + r r r r r r r r r r to get the final value to place
1300 and D D D D D to chop to right size
1301 -----------------------
1304 ... i i i i i o o o o o from bfd_get<size>
1305 and N N N N N get instruction
1306 -----------------------
1312 -----------------------
1313 R R R R R R R R R R put into bfd_put<size>
1317 x = ( (x & ~howto->dst_mask) | (((x & howto->src_mask) + relocation) & howto->dst_mask))
1319 data = (bfd_byte *) data_start + (addr - data_start_offset);
1321 switch (howto->size)
1325 char x = bfd_get_8 (abfd, (char *) data);
1327 bfd_put_8 (abfd, x, (unsigned char *) data);
1333 short x = bfd_get_16 (abfd, (bfd_byte *) data);
1335 bfd_put_16 (abfd, x, (unsigned char *) data);
1340 long x = bfd_get_32 (abfd, (bfd_byte *) data);
1342 bfd_put_32 (abfd, x, (bfd_byte *) data);
1347 long x = bfd_get_32 (abfd, (bfd_byte *) data);
1348 relocation = -relocation;
1350 bfd_put_32 (abfd, x, (bfd_byte *) data);
1360 bfd_vma x = bfd_get_64 (abfd, (bfd_byte *) data);
1362 bfd_put_64 (abfd, x, (bfd_byte *) data);
1366 return bfd_reloc_other;
1372 /* This relocation routine is used by some of the backend linkers.
1373 They do not construct asymbol or arelent structures, so there is no
1374 reason for them to use bfd_perform_relocation. Also,
1375 bfd_perform_relocation is so hacked up it is easier to write a new
1376 function than to try to deal with it.
1378 This routine does a final relocation. It should not be used when
1379 generating relocateable output.
1381 FIXME: This routine ignores any special_function in the HOWTO,
1382 since the existing special_function values have been written for
1383 bfd_perform_relocation.
1385 HOWTO is the reloc howto information.
1386 INPUT_BFD is the BFD which the reloc applies to.
1387 INPUT_SECTION is the section which the reloc applies to.
1388 CONTENTS is the contents of the section.
1389 ADDRESS is the address of the reloc within INPUT_SECTION.
1390 VALUE is the value of the symbol the reloc refers to.
1391 ADDEND is the addend of the reloc. */
1393 bfd_reloc_status_type
1394 _bfd_final_link_relocate (howto, input_bfd, input_section, contents, address,
1396 reloc_howto_type *howto;
1398 asection *input_section;
1406 /* Sanity check the address. */
1407 if (address > input_section->_raw_size)
1408 return bfd_reloc_outofrange;
1410 /* This function assumes that we are dealing with a basic relocation
1411 against a symbol. We want to compute the value of the symbol to
1412 relocate to. This is just VALUE, the value of the symbol, plus
1413 ADDEND, any addend associated with the reloc. */
1414 relocation = value + addend;
1416 /* If the relocation is PC relative, we want to set RELOCATION to
1417 the distance between the symbol (currently in RELOCATION) and the
1418 location we are relocating. Some targets (e.g., i386-aout)
1419 arrange for the contents of the section to be the negative of the
1420 offset of the location within the section; for such targets
1421 pcrel_offset is false. Other targets (e.g., m88kbcs or ELF)
1422 simply leave the contents of the section as zero; for such
1423 targets pcrel_offset is true. If pcrel_offset is false we do not
1424 need to subtract out the offset of the location within the
1425 section (which is just ADDRESS). */
1426 if (howto->pc_relative)
1428 relocation -= (input_section->output_section->vma
1429 + input_section->output_offset);
1430 if (howto->pcrel_offset)
1431 relocation -= address;
1434 return _bfd_relocate_contents (howto, input_bfd, relocation,
1435 contents + address);
1438 /* Relocate a given location using a given value and howto. */
1440 bfd_reloc_status_type
1441 _bfd_relocate_contents (howto, input_bfd, relocation, location)
1442 reloc_howto_type *howto;
1451 /* If the size is negative, negate RELOCATION. This isn't very
1453 if (howto->size < 0)
1454 relocation = -relocation;
1456 /* Get the value we are going to relocate. */
1457 size = bfd_get_reloc_size (howto);
1464 x = bfd_get_8 (input_bfd, location);
1467 x = bfd_get_16 (input_bfd, location);
1470 x = bfd_get_32 (input_bfd, location);
1474 x = bfd_get_64 (input_bfd, location);
1481 /* Check for overflow. FIXME: We may drop bits during the addition
1482 which we don't check for. We must either check at every single
1483 operation, which would be tedious, or we must do the computations
1484 in a type larger than bfd_vma, which would be inefficient. */
1486 if (howto->complain_on_overflow != complain_overflow_dont)
1489 bfd_signed_vma signed_check;
1491 bfd_signed_vma signed_add;
1493 if (howto->rightshift == 0)
1496 signed_check = (bfd_signed_vma) relocation;
1500 /* Drop unwanted bits from the value we are relocating to. */
1501 check = relocation >> howto->rightshift;
1503 /* If this is a signed value, the rightshift just dropped
1504 leading 1 bits (assuming twos complement). */
1505 if ((bfd_signed_vma) relocation >= 0)
1506 signed_check = check;
1508 signed_check = (check
1510 & ~((bfd_vma) - 1 >> howto->rightshift)));
1513 /* Get the value from the object file. */
1514 add = x & howto->src_mask;
1516 /* Get the value from the object file with an appropriate sign.
1517 The expression involving howto->src_mask isolates the upper
1518 bit of src_mask. If that bit is set in the value we are
1519 adding, it is negative, and we subtract out that number times
1520 two. If src_mask includes the highest possible bit, then we
1521 can not get the upper bit, but that does not matter since
1522 signed_add needs no adjustment to become negative in that
1525 if ((add & (((~howto->src_mask) >> 1) & howto->src_mask)) != 0)
1526 signed_add -= (((~howto->src_mask) >> 1) & howto->src_mask) << 1;
1528 /* Add the value from the object file, shifted so that it is a
1530 if (howto->bitpos == 0)
1533 signed_check += signed_add;
1537 check += add >> howto->bitpos;
1539 /* For the signed case we use ADD, rather than SIGNED_ADD,
1540 to avoid warnings from SVR4 cc. This is OK since we
1541 explictly handle the sign bits. */
1542 if (signed_add >= 0)
1543 signed_check += add >> howto->bitpos;
1545 signed_check += ((add >> howto->bitpos)
1547 & ~((bfd_vma) - 1 >> howto->bitpos)));
1550 switch (howto->complain_on_overflow)
1552 case complain_overflow_signed:
1554 /* Assumes two's complement. */
1555 bfd_signed_vma reloc_signed_max = (1 << (howto->bitsize - 1)) - 1;
1556 bfd_signed_vma reloc_signed_min = ~reloc_signed_max;
1558 if (signed_check > reloc_signed_max
1559 || signed_check < reloc_signed_min)
1563 case complain_overflow_unsigned:
1565 /* Assumes two's complement. This expression avoids
1566 overflow if howto->bitsize is the number of bits in
1568 bfd_vma reloc_unsigned_max =
1569 (((1 << (howto->bitsize - 1)) - 1) << 1) | 1;
1571 if (check > reloc_unsigned_max)
1575 case complain_overflow_bitfield:
1577 /* Assumes two's complement. This expression avoids
1578 overflow if howto->bitsize is the number of bits in
1580 bfd_vma reloc_bits = (((1 << (howto->bitsize - 1)) - 1) << 1) | 1;
1582 if ((check & ~reloc_bits) != 0
1583 && (((bfd_vma) signed_check & ~reloc_bits)
1584 != (-1 & ~reloc_bits)))
1593 /* Put RELOCATION in the right bits. */
1594 relocation >>= (bfd_vma) howto->rightshift;
1595 relocation <<= (bfd_vma) howto->bitpos;
1597 /* Add RELOCATION to the right bits of X. */
1598 x = ((x & ~howto->dst_mask)
1599 | (((x & howto->src_mask) + relocation) & howto->dst_mask));
1601 /* Put the relocated value back in the object file. */
1608 bfd_put_8 (input_bfd, x, location);
1611 bfd_put_16 (input_bfd, x, location);
1614 bfd_put_32 (input_bfd, x, location);
1618 bfd_put_64 (input_bfd, x, location);
1625 return overflow ? bfd_reloc_overflow : bfd_reloc_ok;
1631 howto manager, , typedef arelent, Relocations
1636 When an application wants to create a relocation, but doesn't
1637 know what the target machine might call it, it can find out by
1638 using this bit of code.
1647 The insides of a reloc code. The idea is that, eventually, there
1648 will be one enumerator for every type of relocation we ever do.
1649 Pass one of these values to <<bfd_reloc_type_lookup>>, and it'll
1650 return a howto pointer.
1652 This does mean that the application must determine the correct
1653 enumerator value; you can't get a howto pointer from a random set
1672 Basic absolute relocations of N bits.
1687 PC-relative relocations. Sometimes these are relative to the address
1688 of the relocation itself; sometimes they are relative to the start of
1689 the section containing the relocation. It depends on the specific target.
1691 The 24-bit relocation is used in some Intel 960 configurations.
1694 BFD_RELOC_32_GOT_PCREL
1696 BFD_RELOC_16_GOT_PCREL
1698 BFD_RELOC_8_GOT_PCREL
1704 BFD_RELOC_LO16_GOTOFF
1706 BFD_RELOC_HI16_GOTOFF
1708 BFD_RELOC_HI16_S_GOTOFF
1712 BFD_RELOC_32_PLT_PCREL
1714 BFD_RELOC_24_PLT_PCREL
1716 BFD_RELOC_16_PLT_PCREL
1718 BFD_RELOC_8_PLT_PCREL
1724 BFD_RELOC_LO16_PLTOFF
1726 BFD_RELOC_HI16_PLTOFF
1728 BFD_RELOC_HI16_S_PLTOFF
1735 BFD_RELOC_68K_GLOB_DAT
1737 BFD_RELOC_68K_JMP_SLOT
1739 BFD_RELOC_68K_RELATIVE
1741 Relocations used by 68K ELF.
1744 BFD_RELOC_32_BASEREL
1746 BFD_RELOC_16_BASEREL
1748 BFD_RELOC_LO16_BASEREL
1750 BFD_RELOC_HI16_BASEREL
1752 BFD_RELOC_HI16_S_BASEREL
1758 Linkage-table relative.
1763 Absolute 8-bit relocation, but used to form an address like 0xFFnn.
1766 BFD_RELOC_32_PCREL_S2
1768 BFD_RELOC_16_PCREL_S2
1770 BFD_RELOC_23_PCREL_S2
1772 These PC-relative relocations are stored as word displacements --
1773 i.e., byte displacements shifted right two bits. The 30-bit word
1774 displacement (<<32_PCREL_S2>> -- 32 bits, shifted 2) is used on the
1775 SPARC. (SPARC tools generally refer to this as <<WDISP30>>.) The
1776 signed 16-bit displacement is used on the MIPS, and the 23-bit
1777 displacement is used on the Alpha.
1784 High 22 bits and low 10 bits of 32-bit value, placed into lower bits of
1785 the target word. These are used on the SPARC.
1792 For systems that allocate a Global Pointer register, these are
1793 displacements off that register. These relocation types are
1794 handled specially, because the value the register will have is
1795 decided relatively late.
1799 BFD_RELOC_I960_CALLJ
1801 Reloc types used for i960/b.out.
1806 BFD_RELOC_SPARC_WDISP22
1812 BFD_RELOC_SPARC_GOT10
1814 BFD_RELOC_SPARC_GOT13
1816 BFD_RELOC_SPARC_GOT22
1818 BFD_RELOC_SPARC_PC10
1820 BFD_RELOC_SPARC_PC22
1822 BFD_RELOC_SPARC_WPLT30
1824 BFD_RELOC_SPARC_COPY
1826 BFD_RELOC_SPARC_GLOB_DAT
1828 BFD_RELOC_SPARC_JMP_SLOT
1830 BFD_RELOC_SPARC_RELATIVE
1832 BFD_RELOC_SPARC_UA32
1834 SPARC ELF relocations. There is probably some overlap with other
1835 relocation types already defined.
1838 BFD_RELOC_SPARC_BASE13
1840 BFD_RELOC_SPARC_BASE22
1842 I think these are specific to SPARC a.out (e.g., Sun 4).
1852 BFD_RELOC_SPARC_OLO10
1854 BFD_RELOC_SPARC_HH22
1856 BFD_RELOC_SPARC_HM10
1858 BFD_RELOC_SPARC_LM22
1860 BFD_RELOC_SPARC_PC_HH22
1862 BFD_RELOC_SPARC_PC_HM10
1864 BFD_RELOC_SPARC_PC_LM22
1866 BFD_RELOC_SPARC_WDISP16
1868 BFD_RELOC_SPARC_WDISP19
1870 BFD_RELOC_SPARC_GLOB_JMP
1878 Some relocations we're using for SPARC V9 -- subject to change.
1881 BFD_RELOC_ALPHA_GPDISP_HI16
1883 Alpha ECOFF and ELF relocations. Some of these treat the symbol or
1884 "addend" in some special way.
1885 For GPDISP_HI16 ("gpdisp") relocations, the symbol is ignored when
1886 writing; when reading, it will be the absolute section symbol. The
1887 addend is the displacement in bytes of the "lda" instruction from
1888 the "ldah" instruction (which is at the address of this reloc).
1890 BFD_RELOC_ALPHA_GPDISP_LO16
1892 For GPDISP_LO16 ("ignore") relocations, the symbol is handled as
1893 with GPDISP_HI16 relocs. The addend is ignored when writing the
1894 relocations out, and is filled in with the file's GP value on
1895 reading, for convenience.
1898 BFD_RELOC_ALPHA_GPDISP
1900 The ELF GPDISP relocation is exactly the same as the GPDISP_HI16
1901 relocation except that there is no accompanying GPDISP_LO16
1905 BFD_RELOC_ALPHA_LITERAL
1907 BFD_RELOC_ALPHA_LITUSE
1909 The Alpha LITERAL/LITUSE relocs are produced by a symbol reference;
1910 the assembler turns it into a LDQ instruction to load the address of
1911 the symbol, and then fills in a register in the real instruction.
1913 The LITERAL reloc, at the LDQ instruction, refers to the .lita
1914 section symbol. The addend is ignored when writing, but is filled
1915 in with the file's GP value on reading, for convenience, as with the
1918 The LITUSE reloc, on the instruction using the loaded address, gives
1919 information to the linker that it might be able to use to optimize
1920 away some literal section references. The symbol is ignored (read
1921 as the absolute section symbol), and the "addend" indicates the type
1922 of instruction using the register:
1923 1 - "memory" fmt insn
1924 2 - byte-manipulation (byte offset reg)
1925 3 - jsr (target of branch)
1927 The GNU linker currently doesn't do any of this optimizing.
1930 BFD_RELOC_ALPHA_HINT
1932 The HINT relocation indicates a value that should be filled into the
1933 "hint" field of a jmp/jsr/ret instruction, for possible branch-
1934 prediction logic which may be provided on some processors.
1937 BFD_RELOC_ALPHA_LINKAGE
1939 The LINKAGE relocation outputs a linkage pair in the object file,
1940 which is filled by the linker.
1945 Bits 27..2 of the relocation address shifted right 2 bits;
1946 simple reloc otherwise.
1951 High 16 bits of 32-bit value; simple reloc.
1955 High 16 bits of 32-bit value but the low 16 bits will be sign
1956 extended and added to form the final result. If the low 16
1957 bits form a negative number, we need to add one to the high value
1958 to compensate for the borrow when the low bits are added.
1964 BFD_RELOC_PCREL_HI16_S
1966 Like BFD_RELOC_HI16_S, but PC relative.
1968 BFD_RELOC_PCREL_LO16
1970 Like BFD_RELOC_LO16, but PC relative.
1973 BFD_RELOC_MIPS_GPREL
1976 Relocation relative to the global pointer.
1979 BFD_RELOC_MIPS_LITERAL
1981 Relocation against a MIPS literal section.
1984 BFD_RELOC_MIPS_GOT16
1986 BFD_RELOC_MIPS_CALL16
1988 BFD_RELOC_MIPS_GPREL32
1991 BFD_RELOC_MIPS_GOT_HI16
1993 BFD_RELOC_MIPS_GOT_LO16
1995 BFD_RELOC_MIPS_CALL_HI16
1997 BFD_RELOC_MIPS_CALL_LO16
1999 MIPS ELF relocations.
2008 BFD_RELOC_386_GLOB_DAT
2010 BFD_RELOC_386_JUMP_SLOT
2012 BFD_RELOC_386_RELATIVE
2014 BFD_RELOC_386_GOTOFF
2018 i386/elf relocations
2021 BFD_RELOC_NS32K_IMM_8
2023 BFD_RELOC_NS32K_IMM_16
2025 BFD_RELOC_NS32K_IMM_32
2027 BFD_RELOC_NS32K_IMM_8_PCREL
2029 BFD_RELOC_NS32K_IMM_16_PCREL
2031 BFD_RELOC_NS32K_IMM_32_PCREL
2033 BFD_RELOC_NS32K_DISP_8
2035 BFD_RELOC_NS32K_DISP_16
2037 BFD_RELOC_NS32K_DISP_32
2039 BFD_RELOC_NS32K_DISP_8_PCREL
2041 BFD_RELOC_NS32K_DISP_16_PCREL
2043 BFD_RELOC_NS32K_DISP_32_PCREL
2056 BFD_RELOC_PPC_B16_BRTAKEN
2058 BFD_RELOC_PPC_B16_BRNTAKEN
2062 BFD_RELOC_PPC_BA16_BRTAKEN
2064 BFD_RELOC_PPC_BA16_BRNTAKEN
2068 BFD_RELOC_PPC_GLOB_DAT
2070 BFD_RELOC_PPC_JMP_SLOT
2072 BFD_RELOC_PPC_RELATIVE
2074 BFD_RELOC_PPC_LOCAL24PC
2076 BFD_RELOC_PPC_EMB_NADDR32
2078 BFD_RELOC_PPC_EMB_NADDR16
2080 BFD_RELOC_PPC_EMB_NADDR16_LO
2082 BFD_RELOC_PPC_EMB_NADDR16_HI
2084 BFD_RELOC_PPC_EMB_NADDR16_HA
2086 BFD_RELOC_PPC_EMB_SDAI16
2088 BFD_RELOC_PPC_EMB_SDA2I16
2090 BFD_RELOC_PPC_EMB_SDA2REL
2092 BFD_RELOC_PPC_EMB_SDA21
2094 BFD_RELOC_PPC_EMB_MRKREF
2096 BFD_RELOC_PPC_EMB_RELSEC16
2098 BFD_RELOC_PPC_EMB_RELST_LO
2100 BFD_RELOC_PPC_EMB_RELST_HI
2102 BFD_RELOC_PPC_EMB_RELST_HA
2104 BFD_RELOC_PPC_EMB_BIT_FLD
2106 BFD_RELOC_PPC_EMB_RELSDA
2108 Power(rs6000) and PowerPC relocations.
2113 The type of reloc used to build a contructor table - at the moment
2114 probably a 32 bit wide absolute relocation, but the target can choose.
2115 It generally does map to one of the other relocation types.
2118 BFD_RELOC_ARM_PCREL_BRANCH
2120 ARM 26 bit pc-relative branch. The lowest two bits must be zero and are
2121 not stored in the instruction.
2123 BFD_RELOC_ARM_IMMEDIATE
2125 BFD_RELOC_ARM_OFFSET_IMM
2127 BFD_RELOC_ARM_SHIFT_IMM
2133 BFD_RELOC_ARM_CP_OFF_IMM
2135 BFD_RELOC_ARM_ADR_IMM
2137 BFD_RELOC_ARM_LDR_IMM
2139 BFD_RELOC_ARM_LITERAL
2141 BFD_RELOC_ARM_IN_POOL
2143 BFD_RELOC_ARM_OFFSET_IMM8
2145 BFD_RELOC_ARM_HWLITERAL
2147 BFD_RELOC_ARM_THUMB_ADD
2149 BFD_RELOC_ARM_THUMB_IMM
2151 BFD_RELOC_ARM_THUMB_SHIFT
2153 BFD_RELOC_ARM_THUMB_OFFSET
2155 These relocs are only used within the ARM assembler. They are not
2156 (at present) written to any object files.
2159 BFD_RELOC_SH_PCDISP8BY2
2161 BFD_RELOC_SH_PCDISP12BY2
2165 BFD_RELOC_SH_IMM4BY2
2167 BFD_RELOC_SH_IMM4BY4
2171 BFD_RELOC_SH_IMM8BY2
2173 BFD_RELOC_SH_IMM8BY4
2175 BFD_RELOC_SH_PCRELIMM8BY2
2177 BFD_RELOC_SH_PCRELIMM8BY4
2179 BFD_RELOC_SH_SWITCH16
2181 BFD_RELOC_SH_SWITCH32
2195 Hitachi SH relocs. Not all of these appear in object files.
2198 {* start-sanitize-arc *}
2200 BFD_RELOC_ARC_B22_PCREL
2202 Argonaut RISC Core (ARC) relocs.
2203 ARC 22 bit pc-relative branch. The lowest two bits must be zero and are
2204 not stored in the instruction. The high 20 bits are installed in bits 26
2205 through 7 of the instruction.
2209 ARC 26 bit absolute branch. The lowest two bits must be zero and are not
2210 stored in the instruction. The high 24 bits are installed in bits 23
2213 {* end-sanitize-arc *}
2216 {* start-sanitize-d10v *}
2218 BFD_RELOC_D10V_10_PCREL_R
2220 Mitsubishi D10V relocs.
2221 This is a 10-bit reloc with the right 2 bits
2224 BFD_RELOC_D10V_10_PCREL_L
2226 Mitsubishi D10V relocs.
2227 This is a 10-bit reloc with the right 2 bits
2228 assumed to be 0. This is the same as the previous reloc
2229 except it is in the left container, i.e.,
2230 shifted left 15 bits.
2234 This is an 18-bit reloc with the right 2 bits
2237 BFD_RELOC_D10V_18_PCREL
2239 This is an 18-bit reloc with the right 2 bits
2242 {* end-sanitize-d10v *}
2245 {* start-sanitize-m32r *}
2247 BFD_RELOC_M32R_10_PCREL
2249 Mitsubishi M32R relocs.
2250 This is a 10-bit reloc with the right 2 bits assumed to be 0.
2252 BFD_RELOC_M32R_18_PCREL
2254 This is an 18-bit reloc with the right 2 bits assumed to be 0.
2256 BFD_RELOC_M32R_26_PCREL
2258 This is an 26-bit reloc with the right 2 bits assumed to be 0.
2262 This is a 24 bit reloc.
2264 {* end-sanitize-m32r *}
2267 {* start-sanitize-v850 *}
2269 BFD_RELOC_V850_9_PCREL
2271 This is a 9-bit reloc
2273 BFD_RELOC_V850_22_PCREL
2275 This is a 22-bit reloc
2277 {* end-sanitize-v850 *}
2283 .typedef enum bfd_reloc_code_real bfd_reloc_code_real_type;
2289 bfd_reloc_type_lookup
2293 bfd_reloc_type_lookup (bfd *abfd, bfd_reloc_code_real_type code);
2296 Return a pointer to a howto structure which, when
2297 invoked, will perform the relocation @var{code} on data from the
2304 bfd_reloc_type_lookup (abfd, code)
2306 bfd_reloc_code_real_type code;
2308 return BFD_SEND (abfd, reloc_type_lookup, (abfd, code));
2311 static reloc_howto_type bfd_howto_32 =
2312 HOWTO (0, 00, 2, 32, false, 0, complain_overflow_bitfield, 0, "VRT32", false, 0xffffffff, 0xffffffff, true);
2317 bfd_default_reloc_type_lookup
2320 reloc_howto_type *bfd_default_reloc_type_lookup
2321 (bfd *abfd, bfd_reloc_code_real_type code);
2324 Provides a default relocation lookup routine for any architecture.
2330 bfd_default_reloc_type_lookup (abfd, code)
2332 bfd_reloc_code_real_type code;
2336 case BFD_RELOC_CTOR:
2337 /* The type of reloc used in a ctor, which will be as wide as the
2338 address - so either a 64, 32, or 16 bitter. */
2339 switch (bfd_get_arch_info (abfd)->bits_per_address)
2344 return &bfd_howto_32;
2353 return (reloc_howto_type *) NULL;
2358 bfd_get_reloc_code_name
2361 const char *bfd_get_reloc_code_name (bfd_reloc_code_real_type code);
2364 Provides a printable name for the supplied relocation code.
2365 Useful mainly for printing error messages.
2369 bfd_get_reloc_code_name (code)
2370 bfd_reloc_code_real_type code;
2372 if (code > BFD_RELOC_UNUSED)
2374 return bfd_reloc_code_real_names[(int)code];
2379 bfd_generic_relax_section
2382 boolean bfd_generic_relax_section
2385 struct bfd_link_info *,
2389 Provides default handling for relaxing for back ends which
2390 don't do relaxing -- i.e., does nothing.
2395 bfd_generic_relax_section (abfd, section, link_info, again)
2398 struct bfd_link_info *link_info;
2407 bfd_generic_get_relocated_section_contents
2411 bfd_generic_get_relocated_section_contents (bfd *abfd,
2412 struct bfd_link_info *link_info,
2413 struct bfd_link_order *link_order,
2415 boolean relocateable,
2419 Provides default handling of relocation effort for back ends
2420 which can't be bothered to do it efficiently.
2425 bfd_generic_get_relocated_section_contents (abfd, link_info, link_order, data,
2426 relocateable, symbols)
2428 struct bfd_link_info *link_info;
2429 struct bfd_link_order *link_order;
2431 boolean relocateable;
2434 /* Get enough memory to hold the stuff */
2435 bfd *input_bfd = link_order->u.indirect.section->owner;
2436 asection *input_section = link_order->u.indirect.section;
2438 long reloc_size = bfd_get_reloc_upper_bound (input_bfd, input_section);
2439 arelent **reloc_vector = NULL;
2445 reloc_vector = (arelent **) bfd_malloc ((size_t) reloc_size);
2446 if (reloc_vector == NULL && reloc_size != 0)
2449 /* read in the section */
2450 if (!bfd_get_section_contents (input_bfd,
2454 input_section->_raw_size))
2457 /* We're not relaxing the section, so just copy the size info */
2458 input_section->_cooked_size = input_section->_raw_size;
2459 input_section->reloc_done = true;
2461 reloc_count = bfd_canonicalize_reloc (input_bfd,
2465 if (reloc_count < 0)
2468 if (reloc_count > 0)
2471 for (parent = reloc_vector; *parent != (arelent *) NULL;
2474 char *error_message = (char *) NULL;
2475 bfd_reloc_status_type r =
2476 bfd_perform_relocation (input_bfd,
2480 relocateable ? abfd : (bfd *) NULL,
2485 asection *os = input_section->output_section;
2487 /* A partial link, so keep the relocs */
2488 os->orelocation[os->reloc_count] = *parent;
2492 if (r != bfd_reloc_ok)
2496 case bfd_reloc_undefined:
2497 if (!((*link_info->callbacks->undefined_symbol)
2498 (link_info, bfd_asymbol_name (*(*parent)->sym_ptr_ptr),
2499 input_bfd, input_section, (*parent)->address)))
2502 case bfd_reloc_dangerous:
2503 BFD_ASSERT (error_message != (char *) NULL);
2504 if (!((*link_info->callbacks->reloc_dangerous)
2505 (link_info, error_message, input_bfd, input_section,
2506 (*parent)->address)))
2509 case bfd_reloc_overflow:
2510 if (!((*link_info->callbacks->reloc_overflow)
2511 (link_info, bfd_asymbol_name (*(*parent)->sym_ptr_ptr),
2512 (*parent)->howto->name, (*parent)->addend,
2513 input_bfd, input_section, (*parent)->address)))
2516 case bfd_reloc_outofrange:
2525 if (reloc_vector != NULL)
2526 free (reloc_vector);
2530 if (reloc_vector != NULL)
2531 free (reloc_vector);