From: Andrew Haley <aph@redhat.com>
To: Melvin Blades <melvin.blades@gmail.com>
Cc: Ian Lance Taylor <iant@google.com>,
"gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: removing unused functions during final link
Date: Wed, 03 Sep 2014 15:13:00 -0000 [thread overview]
Message-ID: <54073028.9030601@redhat.com> (raw)
In-Reply-To: <CAG=1SRspbFhponeoY1dajoBzvkNJmKPmQuroiggdJJx=gP7avw@mail.gmail.com>
On 09/03/2014 04:09 PM, Melvin Blades wrote:
> The resulting executable contains the texts strings and function names
> from both functions in show.c and neither function of show2.c My
> usage of -fdata-section -ffunction-section and -gc-sections prevents
> the functions in show2.c from being linked in , but not the unused
> functions in show.c
Something must be referring to them; they must be reachable.
That or there's a bug.
There's no way for anyone to know without seeing code.
Andrew.
next prev parent reply other threads:[~2014-09-03 15:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 21:02 Melvin Blades
2014-08-27 21:22 ` Ian Lance Taylor
2014-09-03 3:20 ` Melvin Blades
2014-09-03 10:21 ` Andrew Haley
2014-09-03 15:09 ` Melvin Blades
2014-09-03 15:13 ` Andrew Haley [this message]
2014-09-05 15:24 ` Melvin Blades
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=54073028.9030601@redhat.com \
--to=aph@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=iant@google.com \
--cc=melvin.blades@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).