From: xunxun <xunxun1982@gmail.com>
To: nick clifton <nickc@redhat.com>
Cc: Kai Tietz <ktietz70@googlemail.com>, Binutils <binutils@sourceware.org>
Subject: Re: [patch ld]: Fix for bug ld/11539: ld --gc-sections should work for PE-COFF on MinGW
Date: Wed, 22 Aug 2012 01:47:00 -0000 [thread overview]
Message-ID: <50342ED3.8040007@gmail.com> (raw)
In-Reply-To: <5033B63A.50504@redhat.com>
äº 2012/8/22 0:24, nick clifton åé:
> Hi Guys,
>
>> Ping?
>
> I looked at this, but I was not sure exactly which patch is the final
> version. Can you point me at it please, so that I can review it ?
>
> Cheers
> Nick
>
>
I want to say Kai's patch is not complete, which only modify linker
script ( this won't make --gc-sections be valid ), so I think Kai must
add other section's patches such as libbfd ( PR11539 has the libbfd
initial patch ).
--
Best Regards,
xunxun
next prev parent reply other threads:[~2012-08-22 0:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 12:42 Kai Tietz
2012-08-14 8:06 ` xunxun
2012-08-14 12:11 ` Kai Tietz
2012-08-15 17:18 ` xunxun
2012-08-20 3:32 ` xunxun
2012-08-21 19:01 ` nick clifton
2012-08-22 1:47 ` xunxun [this message]
2012-08-22 17:09 ` Kai Tietz
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=50342ED3.8040007@gmail.com \
--to=xunxun1982@gmail.com \
--cc=binutils@sourceware.org \
--cc=ktietz70@googlemail.com \
--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).