This is the mail archive of the
mailing list for the binutils project.
RE: ordinal linking for cygwin ld
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- To: "Ralf Habacker" <Ralf dot Habacker at freenet dot de>,<kde-cygwin at mail dot kde dot org>,"Charles Wilson" <cwilson at ece dot gatech dot edu>
- Cc: "Binutils" <binutils at sources dot redhat dot com>,"Cygwin-Apps" <cygwin-apps at cygwin dot com>
- Date: Sun, 28 Apr 2002 22:21:59 +1000
- Subject: RE: ordinal linking for cygwin ld
> -----Original Message-----
> From: Ralf Habacker [mailto:Ralf.Habacker@freenet.de]
> Sent: Sunday, April 28, 2002 10:18 PM
> Firstthunk points to 0x401064, the symbol <__fu0__var0000>,
> which is the address part of the mov instruction. After run
> time linking the loader has relocated this address to the
> propper value.
Ok, I see what it does. Doesn't it have to do that for each reference to
the auto-imported variable? If so, then heavy use of an imported
variable could make the INT and IAT quite large - and lots of fixups
needed. However, binding could still work, as we effectively have a
pointer to each address reference in the binary.