From: DJ Delorie <dj@delorie.com>
To: cwilson@ece.gatech.edu
Cc: binutils@sources.redhat.com, cygwin@cygwin.com
Subject: Re: [aida_s@mx12.freecom.ne.jp: A serious bug of "ld --enable-auto-import"]
Date: Sat, 25 Aug 2001 23:14:00 -0000 [thread overview]
Message-ID: <200108260613.CAA28557@envy.delorie.com> (raw)
In-Reply-To: <3B888D76.6090102@ece.gatech.edu>
> Anyway, I'm confused. The .o file already contains the "12" (actually,
> 0c 00 00 00 in on-disk byte order), so gas has already done its work --
> properly. The problem occurs during the linking step -- ld is ignoring
> the offset stored within the opcode and is blindly stuffing in the
> relocation address without adding the offset.
Ok, a couple of things:
In make_import_fixup in ld/emultempl/pe.em, it uses rel->addend
without also checking for the inline offset. For formats that use an
inline addend, rel->addend may be zero.
Addends are very tricky in PE. There's lots of comments about adding,
subtracting, adding, subtracting, etc, in various places in the code.
I don't think an import library *can* specify an offset to be added at
runtime. From my understanding of the dll import/export system,
windows simply places the address of the thing being imported in the
location indicated.
next prev parent reply other threads:[~2001-08-25 23:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-25 22:11 Charles S. Wilson
2001-08-25 22:30 ` DJ Delorie
2001-08-25 22:47 ` Charles Wilson
2001-08-25 23:14 ` DJ Delorie [this message]
2001-08-26 8:10 ` Charles Wilson
2001-08-26 8:43 ` DJ Delorie
2001-08-26 9:04 ` Charles Wilson
2001-08-26 9:43 ` DJ Delorie
2001-08-26 15:35 ` Charles Wilson
2001-08-26 12:27 ` Kurt Roeckx
-- strict thread matches above, loose matches on Subject: below --
2001-08-25 10:50 Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200108260613.CAA28557@envy.delorie.com \
--to=dj@delorie.com \
--cc=binutils@sources.redhat.com \
--cc=cwilson@ece.gatech.edu \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).