From: Werner Almesberger <Werner.Almesberger@epfl.ch>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: beware of dead string constants
Date: Thu, 23 Nov 2000 14:06:30 +0100 [thread overview]
Message-ID: <20001123140630.F599@almesberger.net> (raw)
In-Reply-To: <200011221848.MAA05565@duracef.shout.net>
In-Reply-To: <200011221848.MAA05565@duracef.shout.net>; from mec@shout.net on Wed, Nov 22, 2000 at 12:48:30PM -0600
Michael Elizabeth Chastain wrote:
> I have a compiler from gcc.gnu.org's CVS tree that's only a few days old,
> so I can verify Jakub's claim.
BTW, do you have any estimate of how much dead string space it actually
removed ? (I.e. did the .data segment size change significantly, or was
is lost in the normal inter-gcc-version noise ?)
Just curious,
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, ICA, EPFL, CH Werner.Almesberger@epfl.ch /
/_IN_N_032__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/
-
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-23 13:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-22 18:48 beware of dead string constants Michael Elizabeth Chastain
2000-11-23 13:06 ` Werner Almesberger [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-26 14:29 Bernd Eckenfels
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-21 12:02 Peter Samuelson
2000-11-21 12:13 ` Jakub Jelinek
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
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=20001123140630.F599@almesberger.net \
--to=werner.almesberger@epfl.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=mec@shout.net \
/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