From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Bernd Eckenfels <ecki-lkm@lina.inka.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make gcc3.3 Eliminate Unused Static Functions
Date: Fri, 13 Jun 2003 10:04:56 -0400 [thread overview]
Message-ID: <3EE9DA08.2020707@nortelnetworks.com> (raw)
In-Reply-To: E19Qeoz-0004CM-00@calista.inka.de
Bernd Eckenfels wrote:
> does that mean the current linux source tree does not benefit in any way
> from this patch?
I suspect that currently all such instances are wrapped in #ifdef and are not
currently compiled in. As he said in the original message, "it'd be nice to
discard unused functions (think CONFIG_PROC_FS=n) without needing to #ifdef
around them."
This would allow us to remove those #ifdefs.
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2003-06-13 13:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 0:17 [PATCH] Make gcc3.3 Eliminate Unused Static Functions Rusty Russell
2003-06-13 3:01 ` Bernd Eckenfels
2003-06-13 14:04 ` Chris Friesen [this message]
2003-06-13 16:03 ` Tom Rini
2003-06-13 18:07 ` Robert Love
2003-06-13 18:15 ` Tom Rini
2003-06-13 18:41 ` Robert Love
2003-06-19 12:10 ` Adrian Bunk
2003-06-19 13:28 ` Jörn Engel
2003-06-19 13:57 ` Bob Tracy
2003-06-19 14:32 ` Chris Meadors
-- strict thread matches above, loose matches on Subject: below --
2003-06-13 1:03 Rusty Russell
2003-06-19 12:17 ` Adrian Bunk
2003-06-20 2:28 ` Rusty Russell
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=3EE9DA08.2020707@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=ecki-lkm@lina.inka.de \
--cc=linux-kernel@vger.kernel.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