Mail Archives: djgpp-workers/1996/06/22/13:03:02
> After a look at the specs I suspect this is because gcc calls stubify
> after ld created the COFF image. Is this true ?
This is correct, yes, and does contribute to the slowness.
> If yes, would it be much work to add the functionality
> of stubify to ld if the output file ends in '.exe',
> thereby saving a write and read of the image ?
This is what DJ calls "teaching BFD about the stub". Once the GNU routines
are fixed to know about the stub, all sorts of good things happen, like
size/strip/gdb can handled stubbed .EXE images, ld could write the stub
directly, etc. So far noone has had the time and energy to make these
changes and submit them to the FSF.
- Raw text -