From: Andrew Cagney <ac131313@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb@sources.redhat.com
Subject: Re: 20% space savings!
Date: Wed, 20 Aug 2003 16:29:00 -0000 [thread overview]
Message-ID: <3F43A1E0.4070609@redhat.com> (raw)
In-Reply-To: <200308191814.h7JIETLn022619@duracef.shout.net>
> I pulled a Daniel Berlin last night (in a good way) and started
> packing structures like a #4 train at rush hour.
>
> 'maint space' has gone from:
>
> before: 99352576
> after: 79478784
>
> It would take a lot of time to merge these patches into gdb.
> I would have to write up a road map, and then test the patches
> one at a time (that is the hard part, regression testing stuff
> like coff), then submit the patches one at a time to the
> symtab maintainers.
>
> Is this something worth pursuing?
This will definitly help short term. Long term, to abuse an ad, "While
amazing, it's not sensational[sp?]". As David and Elena work through an
overhaul of the symbol table and a better understanding of what it
really needs to do is gained, a more radical approach can be taken.
Andrew
next prev parent reply other threads:[~2003-08-20 16:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 18:14 Michael Elizabeth Chastain
2003-08-19 18:29 ` Kevin Buettner
2003-08-19 18:30 ` Daniel Jacobowitz
2003-08-20 16:29 ` Andrew Cagney [this message]
2003-08-20 17:09 ` User defined commands jacques
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=3F43A1E0.4070609@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).