Lines Matching full:coff
89 . generated only when linking i960 coff files with i960 b.out
178 Using coff and an 88k, some instructions don't have enough
289 . in a coff environment has the type 023 - because that's
562 basic coff) have no way of specifying an addend in the
715 && strcmp (abfd->xvec->name, "coff-Intel-little") != 0
716 && strcmp (abfd->xvec->name, "coff-Intel-big") != 0)
718 /* For m68k-coff, the addend was being subtracted twice during
725 If you put a patch like that into BFD you need to check all the COFF
726 linkers. I am fairly certain that patch will break coff-i386 (e.g.,
727 SCO); see coff_i386_reloc in coff-i386.c where I worked around the
735 relocatable output for COFF. That's peculiar. In fact, I really
738 A typical COFF reloc subtracts the old value of the symbol and adds in
747 compatibility with old object files) (coff-i386 does subtract the old
748 value, to be compatible with existing coff-i386 targets, like SCO).
755 add the value into the object file. This won't hurt the COFF code,
760 When I wanted to make coff-i386 produce relocatable output, I ran
762 line. Rather than risk it, I made the coff-i386 relocs use a special
763 function; it's coff_i386_reloc in coff-i386.c. The function
766 coff-i386.c will wind up adding the addend field in twice. It's
772 supported COFF targets. It should be straightforward if time and disk
1096 && strcmp (abfd->xvec->name, "coff-Intel-little") != 0
1097 && strcmp (abfd->xvec->name, "coff-Intel-big") != 0)
1100 /* For m68k-coff, the addend was being subtracted twice during
1107 If you put a patch like that into BFD you need to check all the COFF
1108 linkers. I am fairly certain that patch will break coff-i386 (e.g.,
1109 SCO); see coff_i386_reloc in coff-i386.c where I worked around the
1117 relocatable output for COFF. That's peculiar. In fact, I really
1120 A typical COFF reloc subtracts the old value of the symbol and adds in
1129 compatibility with old object files) (coff-i386 does subtract the old
1130 value, to be compatible with existing coff-i386 targets, like SCO).
1137 add the value into the object file. This won't hurt the COFF code,
1142 When I wanted to make coff-i386 produce relocatable output, I ran
1144 line. Rather than risk it, I made the coff-i386 relocs use a special
1145 function; it's coff_i386_reloc in coff-i386.c. The function
1148 coff-i386.c will wind up adding the addend field in twice. It's
1154 supported COFF targets. It should be straightforward if time and disk
1170 if (strcmp (abfd->xvec->name, "coff-z8k") != 0)
