From: Jakub Jelinek <jakub@redhat.com>
To: Peter Samuelson <peter@cadcamlab.org>
Cc: jgarzik@mandrakesoft.com, linux-kernel@vger.kernel.org
Subject: Re: beware of dead string constants
Date: Tue, 21 Nov 2000 07:13:27 -0500 [thread overview]
Message-ID: <20001121071327.R1514@devserv.devel.redhat.com> (raw)
In-Reply-To: <14874.25691.629724.306563@wire.cadcamlab.org>
In-Reply-To: <14874.25691.629724.306563@wire.cadcamlab.org>; from peter@cadcamlab.org on Tue, Nov 21, 2000 at 06:02:35AM -0600
On Tue, Nov 21, 2000 at 06:02:35AM -0600, Peter Samuelson wrote:
>
> While trying to clean up some code recently (CONFIG_MCA, hi Jeff), I
> discovered that gcc 2.95.2 (i386) does not remove dead string
> constants:
>
> void foo (void)
> {
> if (0)
> printk(KERN_INFO "bar");
> }
>
> Annoyingly, gcc forgets to drop the "<6>bar\0". It shows up in the
> object file, needlessly clogging your cachelines.
gcc was never dropping such strings, I've commited a patch to fix this
a week ago into CVS.
Jakub
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-21 12:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 12:02 beware of dead string constants Peter Samuelson
2000-11-21 12:13 ` Jakub Jelinek [this message]
2000-11-21 12:24 ` Peter Samuelson
2000-11-21 20:51 ` J . A . Magallon
2000-11-22 1:14 ` Peter Samuelson
2000-11-22 8:27 ` Urban Widmark
-- strict thread matches above, loose matches on Subject: below --
2000-11-22 18:48 Michael Elizabeth Chastain
2000-11-23 13:06 ` Werner Almesberger
2000-11-23 23:29 Bernd Eckenfels
2000-11-23 23:39 ` Jeff Garzik
2000-11-24 3:36 ` Peter Samuelson
2000-11-24 4:15 ` Chris Wedgwood
2000-11-26 14:29 Bernd Eckenfels
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=20001121071327.R1514@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@cadcamlab.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.