From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jeffrey Karl Lassahn <jkl@teleport.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: dead code removal
Date: Sat, 18 Dec 1999 12:08:59 -0800 (PST) [thread overview]
Message-ID: <XFMail.991218120859.jeremy@goop.org> (raw)
In-Reply-To: <Pine.GSO.4.10.9911251429370.12868-100000@user2.teleport.com>
On 25-Nov-99 Jeffrey Karl Lassahn wrote:
> In principle it can be if the function is marked static (so the compiler
> knows it will never link outside the module.) Does anyone know if GCC
> does remove the code in this case?
No, only if its inline. Just because the compiler can't see a reference, it
doesn't mean one isn't there - inline assember may refer to the static function.
Basically, you need the linker to strip dead functions, because nothing else
has enough information to do it right.
J
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~1999-12-18 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-25 1:10 dead code removal Jim Reekes
1999-11-25 6:53 ` Daniel Jacobowitz
1999-11-25 22:32 ` Jeffrey Karl Lassahn
1999-12-18 20:08 ` Jeremy Fitzhardinge [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=XFMail.991218120859.jeremy@goop.org \
--to=jeremy@goop.org \
--cc=jkl@teleport.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).