From: Nick Clifton <nickc@redhat.com>
To: "H. J. Lu" <hjl@lucon.org>, Marcelo Tosatti <marcelo@kvack.org>
Cc: binutils@sources.redhat.com
Subject: Re: [binutils patch]: -print-gc-sections option: print garbage collected sections
Date: Fri, 04 Aug 2006 14:50:00 -0000 [thread overview]
Message-ID: <44D35EA1.3060603@redhat.com> (raw)
In-Reply-To: <20060707222120.GA29900@lucon.org>
Hi H.J., Hi Marcelo,
> I am forwarding it to the binutils mailing list.
I apologise for taking so long to getting round to reviewing this patch.
As it stands the patch is OK, but incomplete. So I have taken the
liberty of applying it along with the following changes:
* I added a --no-print-gc-sections switch so that the option can be
turned off.
* I added documentation to the ld.texinfo file describing the new
switches.
* I added an entry to the ld/NEWS file describing the new feature.
* I changed the message that is printed so that it explicitly states
that it is telling the user about a deleted section, and I used the
bfd error handler routine so that the correct filename can be
displayed.
* I created a set of ChangeLog entries for the patch.
Cheers
Nick
ld/ChangeLog
2006-08-04 Marcelo Tosatti <marcelo@kvack.org>
* ldmain.c (main): Initialise print_gc_sections field of link_info
structure.
* lexsup.c: Add --print-gc-sections and --no-print-gc-sections
switches.
* ld.texinfo: Document new switches.
* NEWS: Mention new switches.
include/ChangeLog
2006-08-04 Marcelo Tosatti <marcelo@kvack.org>
* bfdlink.h (struct bfd_link_info): New field: print_gc_sections.
bfd/ChangeLog
2006-08-04 Marcelo Tosatti <marcelo@kvack.org>
* elflink.c (elf_gc_sweep): If info.print_gc_sections is true,
list removed sections to stderr.
prev parent reply other threads:[~2006-08-04 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060701231428.GA23415@dmt>
2006-07-07 22:21 ` H. J. Lu
2006-08-04 14:50 ` Nick Clifton [this message]
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=44D35EA1.3060603@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=hjl@lucon.org \
--cc=marcelo@kvack.org \
/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).