From: Nick Clifton <nickc@redhat.com>
To: cwilson@ece.gatech.edu, deo@logos-m.ru
Cc: binutils@sources.redhat.com, cygwin-apps@cygwin.com
Subject: Re: --enable-auto-import extension
Date: Thu, 14 Nov 2002 10:07:00 -0000 [thread overview]
Message-ID: <m3u1ik3r5z.fsf@north-pole.nickc.cambridge.redhat.com> (raw)
In-Reply-To: <3DD01AB3.3060906@ece.gatech.edu>
Hi Charles, Hi Egor,
> 2002-07-01 Egor Duda <deo@logos-m.ru>
>
> * ldmain.c (main): Make runtime relocs disabled by default. Remove
> assignment which has no effect.
> * pe-dll.h (pe_create_import_fixup): Change prototype.
> * pe-dll.c (make_runtime_pseudo_reloc): New function.
> (pe_create_runtime_relocator_reference): Ditto.
> (pe_create_import_fixup): Handle relocations with non-zero addends.
> * emultempl/pe.em: Add options --enable-runtime-pseudo-reloc and
> --disable-runtime-pseudo-reloc.
> (make_import_fixup): Handle relocations with non-zero addends. Create
> an external reference to _pei386_runtime_relocator symbol if at least
> one pseudo reloc was created.
> * ld.texinfo: Document --enable-runtime-pseudo-reloc and
> --disable-runtime-pseudo-reloc options.
> 2002-07-01 Egor Duda <deo@logos-m.ru>
>
> * bfdlink.h (struct bfd_link_info): Add new boolean
> field pei386_runtime_pseudo_reloc.
Approved and applied. [Sorry for the long delay].
Note: The cygwin targeted ports (eg i686-pc-cygwin) are currently
showing three unexpected failures in the GAS testsuite:
FAIL: i386 abs reloc
FAIL: i386 pcrel reloc
FAIL: i386 sub
Which their non-PE cousins do not. I would appreciate it if you could
spare a few moments to investigate this.
Cheers
Nick
next prev parent reply other threads:[~2002-11-14 18:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 18:01 Charles Wilson
2002-11-14 10:07 ` Nick Clifton [this message]
2002-11-15 5:35 ` egor duda
-- strict thread matches above, loose matches on Subject: below --
2002-06-28 3:19 egor duda
2002-06-28 18:08 ` Charles Wilson
2002-06-30 23:47 ` egor duda
2002-07-01 14:28 ` Charles Wilson
2002-07-02 8:39 ` egor duda
2002-07-02 9:31 ` Christopher Faylor
2002-07-03 2:21 ` egor duda
2002-07-03 12:05 ` Charles Wilson
2002-07-04 3:43 ` egor duda
2002-08-15 10:49 ` Christopher Faylor
2002-08-15 23:21 ` egor duda
2002-07-07 18:20 ` David A. Cobb
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=m3u1ik3r5z.fsf@north-pole.nickc.cambridge.redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=cwilson@ece.gatech.edu \
--cc=cygwin-apps@cygwin.com \
--cc=deo@logos-m.ru \
/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).