From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Nick Clifton <nickc@redhat.com>,
binutils@sourceware.org, Kai Tietz <Kai.Tietz@onevision.com>
Subject: Re: PING: patch: Update of pep x86_64 support of ld
Date: Mon, 06 Aug 2007 11:31:00 -0000 [thread overview]
Message-ID: <20070806113208.GA21109@ednor.casa.cgf.cx> (raw)
In-Reply-To: <OFB5CE4F83.021776BF-ONC125732F.0029510A-C125732F.0029869E@onevision.de>
On Mon, Aug 06, 2007 at 09:33:34AM +0200, Kai Tietz wrote:
>Hi,
>
>I recognized some troubles in the pe+ support for x86_64 mingw target. It
>warns about '@xx' stuff passed by gcc, but this can be silently ignored by
>setting 'pep_enable_stdcall_fixup' to true for now. In near future when I
>fix spec definition of gcc, the related around 'pep_enable_stdcall_fixup'
>can be removed completly for this target (There are no '@xx' for this
>target at all). I updated for this target the autofilter_symbollist_i386
>list, too.
>
>Further I detected that the test-case of ld-pe : direct fails, because the
>shared object detection wasn't merged from pe to pep.
>
>Tested for x86_64-pc-mingw32 and cygwin without new regressions.
>
>ChangeLog for ld
>
>2007-07-24 Kai Tietz <kai.tietz@onevision.com>
>
> * emultempl/pep.em: (pep_enable_stdcall_fixup): Set to value 1.
> gld_xxx_recognized_file: Use pep_bfd_is_dll for detection of
>shared
> objects.
> * pe-dll.c: (autofilter_symbollist_i386): Define set
> for amd64 mingw target.
Looks ok to me. Go ahead and checkin.
cgf
next prev parent reply other threads:[~2007-08-06 11:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 7:34 Kai Tietz
2007-08-06 11:31 ` Christopher Faylor [this message]
2007-08-06 11:55 ` Kai Tietz
2007-08-06 14:33 ` Nick Clifton
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=20070806113208.GA21109@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=Kai.Tietz@onevision.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.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).