Mail Archives: cygwin-apps/2002/04/26/20:56:04
> -----Original Message-----
> From: binutils-owner AT sources DOT redhat DOT com
> [mailto:binutils-owner AT sources DOT redhat DOT com]On Behalf Of Robert Collins
> Sent: Saturday, April 27, 2002 2:26 AM
> To: Ralf Habacker; Charles Wilson
> Cc: Kde-Cygwin; Binutils; Cygwin-Apps
> Subject: RE: ordinal linking for cygwin ld
> > -----Original Message-----
> > From: Ralf Habacker [mailto:Ralf DOT Habacker AT freenet DOT de]
> > Sent: Saturday, April 27, 2002 10:23 AM
> > To: Robert Collins; Charles Wilson
> > Cc: Kde-Cygwin; Binutils; Cygwin-Apps
> > Subject: RE: ordinal linking for cygwin ld
> > > The PE spec (as I read it) indicates that as long as a name is
> > > included (ie it's not link-only-by-ordinal) then ordinals
> > can change
> > > and nothing will break.
> > >
> > > It's only when the only link information is the ordinal
> > that problems
> > > will appear.
> > Or ld has a switch to explicit use ordinals (see other mails from me)
> I don't see what such a switch gains. The hint ordinal should provide
> the same performance as an ordinal-only-link.
By default ld does not use ordinals or linking. Only when an import lib does not
contain names in the _nm_vector, ld takes the ordinal for linking (identified by
flag_noname in pe-dll.c/ei386pe.c).
Thats what I have used. I have patched ld to write the import library only with
ordinals and ld does the rest.
Only an additional patch for auto-imported date was necessary. (see the patch)
- Raw text -