public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@adacore.com>
To: Alan Modra <amodra@bigpond.net.au>
Cc: binutils@gcc.gnu.org,  Arnaud Charlet <charlet@adacore.com>
Subject: Re: [PATCH] New option --print-gc-sections
Date: Mon, 03 Apr 2006 06:36:00 -0000	[thread overview]
Message-ID: <200604030839.41118.ebotcazou@adacore.com> (raw)
In-Reply-To: <20060329124950.GD22754@bubble.grove.modra.org>

> Actually, you can already glean this from a link map.  GC'd sections
> will be those that are shown with zero size.

That doesn't seem to work.  Even if I remove the "if (size != 0)" at the 
beginning of print_input_section, the interesting sections are not present in 
the link map.

On my example, a grep "unused" should have returned .text.u__unused, 
.text.u__unused2 and .gcc_except_table.u__unused, whereas I only see

 .rel.text.u__unused
                0x0000000008049088        0x0 /usr/lib/crt1.o
 .rel.text.u__unused_2
                0x0000000008049088        0x0 /usr/lib/crt1.o
 .rel.gcc_except_table.u__unused
                0x00000000080490f8        0x0 /usr/lib/crt1.o

-- 
Eric Botcazou

  reply	other threads:[~2006-04-03  6:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28 12:04 Eric Botcazou
2006-03-29 14:31 ` Alan Modra
2006-04-03  6:36   ` Eric Botcazou [this message]
2006-04-03  7:50     ` Alan Modra
2006-04-04  7:57       ` Eric Botcazou
2006-04-04  8:30         ` Alan Modra
2006-04-04  9:08           ` Eric Botcazou
2006-04-05  3:34             ` Alan Modra
2006-04-05  7:48               ` Eric Botcazou
2006-04-05 15:34                 ` Alan Modra
2006-04-05 15:52                   ` Eric Botcazou
2006-04-05 15:55                     ` Alan Modra
2006-04-05 16:05                       ` Eric Botcazou
2006-04-05 17:44                         ` Alan Modra

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=200604030839.41118.ebotcazou@adacore.com \
    --to=ebotcazou@adacore.com \
    --cc=amodra@bigpond.net.au \
    --cc=binutils@gcc.gnu.org \
    --cc=charlet@adacore.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).