From: David Carlton <carlton@kealia.com>
To: Jim Blandy <jimb@redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
Michael Snyder <msnyder@redhat.com>,
Michael Elizabeth Chastain <mec@shout.net>,
ezannoni@redhat.com, gdb-patches@sources.redhat.com,
ac131313@redhat.com
Subject: Re: [rfa] save space by using enum bitfields
Date: Mon, 18 Aug 2003 21:50:00 -0000 [thread overview]
Message-ID: <yf2r83iab4d.fsf@hawaii.kealia.com> (raw)
In-Reply-To: <vt2r83iwsan.fsf@zenia.home> (Jim Blandy's message of "18 Aug 2003 16:48:48 -0500")
On 18 Aug 2003 16:48:48 -0500, Jim Blandy <jimb@redhat.com> said:
> Daniel Jacobowitz <drow@mvista.com> writes:
>> Well, I'd say that 20% off the size of struct symbol is pretty
>> good. It makes the idea of unifying our symbol tables to have only
>> one kind of symbol much more practical.
> Given that Michael C. says it only saves 0.6% when debugging GDB
> itself, why do you say the size reductions are significant?
For what it's worth, his test wouldn't have noticed size reduction in
struct symbol, only in struct {partial,minimal}_symbol. But 0.6%
seems pretty small either way.
David Carlton
carlton@kealia.com
next prev parent reply other threads:[~2003-08-18 21:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 7:00 Michael Elizabeth Chastain
2003-08-18 20:50 ` Michael Snyder
2003-08-18 20:56 ` Daniel Jacobowitz
2003-08-18 21:47 ` Jim Blandy
2003-08-18 21:50 ` David Carlton [this message]
2003-08-18 21:53 ` Daniel Jacobowitz
2003-08-18 21:06 ` David Carlton
2003-08-18 22:07 Michael Elizabeth Chastain
2003-08-18 23:02 ` Andrew Cagney
2003-08-18 22:35 Michael Elizabeth Chastain
2003-08-19 19:25 ` Jim Blandy
2003-08-19 19:38 Michael Elizabeth Chastain
2003-08-19 21:57 ` Jim Blandy
2003-08-19 19:42 Michael Elizabeth Chastain
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=yf2r83iab4d.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=mec@shout.net \
--cc=msnyder@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