From: Kai Tietz <ktietz70@googlemail.com>
To: xunxun <xunxun1982@gmail.com>
Cc: Binutils <binutils@sourceware.org>, Nick Clifton <nickc@redhat.com>
Subject: Re: [patch ld]: Fix for bug ld/11539: ld --gc-sections should work for PE-COFF on MinGW
Date: Tue, 14 Aug 2012 12:11:00 -0000 [thread overview]
Message-ID: <CAEwic4ZRfPLVYYznZoF5X_CxZvZh9d=7hOdLwHX9pZt58QG+ag@mail.gmail.com> (raw)
In-Reply-To: <502A03B3.2030809@gmail.com>
2012/8/14 xunxun <xunxun1982@gmail.com>:
> Hello, Kai
>
> 于 2012/8/13 20:37, Kai Tietz 写道:
>
>> Hello,
>>
>> This patch addresses for pe-coff and pe+-coff the issue reported about
>> --gc-sections.
>>
>>
> I notice that the patch only modifies the linker script
>
> I remembered --gc-sections option is ignored by the linker on MinGW, so to
> enable the option also should modify libbfd?
> I saw the initial patch in ld/11539 also modify bfd, but I don't know
> whether the bfd part is fixed now.
Ok, I will take a look for it.
>
>
> And you also added
>
> KEEP(*(.eh_frame*))
>
> When I tested the KEEP half one year ago, I really found KEEP(*(.eh_frame*))
> can make all --gc-sections target to work, but exe target using the KEEP
> will increase the size. Can we only use the KEEP to dll target?
Well, that size is increasing here I had expected. The issue is that
some dups aren't anylonger removed from link. Not sure if I can limit
this linker-script to use keep on dll-target only. It doesn't sound
sane to me to do that.
Regards,
Kai
next prev parent reply other threads:[~2012-08-14 8:06 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 [this message]
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
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='CAEwic4ZRfPLVYYznZoF5X_CxZvZh9d=7hOdLwHX9pZt58QG+ag@mail.gmail.com' \
--to=ktietz70@googlemail.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
--cc=xunxun1982@gmail.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).