From: Daniel Jacobowitz <drow@false.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: shrink minimal symbols
Date: Wed, 27 Aug 2008 20:58:00 -0000 [thread overview]
Message-ID: <20080827205745.GA10837@caradoc.them.org> (raw)
In-Reply-To: <m3ljyi449t.fsf@fleche.redhat.com>
On Wed, Aug 27, 2008 at 02:00:30PM -0600, Tom Tromey wrote:
> I consistently see memory reductions of 4-8%. Some figures:
>
> Program Before After %
>
> OO.o 73490432 70692864 3.8
> firefox 35336192 32542720 7.9
> libgcj 15466496 14970880 3.2
The OO.o/firefox numbers are with shared libraries loaded, I assume.
Do you have any performance comparison? I'm not too worried about
lookup performance - number of lookups is relatively low though with
full debug info I'd expect it to be linear to the number of minimal
symbols. But I am concerned about startup time.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-08-27 20:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 20:01 Tom Tromey
2008-08-27 20:58 ` Daniel Jacobowitz [this message]
2008-08-27 22:48 ` Tom Tromey
2008-08-28 1:40 ` Daniel Jacobowitz
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=20080827205745.GA10837@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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