From: Jim Reekes <reekes@kerbango.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: dead code removal
Date: Wed, 24 Nov 1999 17:10:03 -0800 [thread overview]
Message-ID: <383C8C6B.97F4CF60@kerbango.com> (raw)
I have a little program that contains a routine DummyFunc() which is
never reference in the code. Building this single source file in any way
I've tried results in a binary which contains DummyFunc(). Using nm and
objdump, as far as I can determine GCC 2.95 does not dead-code strip.
(which I find amazing!). So I have two questions.
Am I missing something and GCC actually does dead-code stripping?
- or -
How can I find unused/unreferenced symbols in my code so that I can bury
the dead code manually?
Jim
P.S. I have always compared programming to ditch digging, and now I'm
convinced.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-11-25 1:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-25 1:10 Jim Reekes [this message]
1999-11-25 6:53 ` dead code removal Daniel Jacobowitz
1999-11-25 22:32 ` Jeffrey Karl Lassahn
1999-12-18 20:08 ` Jeremy Fitzhardinge
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=383C8C6B.97F4CF60@kerbango.com \
--to=reekes@kerbango.com \
--cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).