From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: gdb@sources.redhat.com
Subject: Re: improving psymtab generation memory usage
Date: Thu, 19 Jul 2001 09:48:00 -0000 [thread overview]
Message-ID: <npwv54uanl.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <87wv54apc5.fsf@cgsoftware.com>
Daniel Berlin <dan@cgsoftware.com> writes:
> > So what I'm saying is, we should be able to cut partial symbol table
> > generation memory usage to a minimum by adding one call to
> > obstack_free in scan_partial_symbols.
>
> Sure, for psymbols, this will work fine.
> For full symbols, it won't.
> I did the full symbol elimination first, then psymbols, so i just used
> the full symbol approach scaled down.
Sure, and that seems reasonable. I'm just checking my understanding
with someone who's been down the path before.
I'm going to make my change, simply because it's small, and will at
least help somewhat until we can do more.
prev parent reply other threads:[~2001-07-19 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-18 15:58 Jim Blandy
2001-07-18 22:34 ` Daniel Berlin
2001-07-19 8:43 ` Jim Blandy
2001-07-19 8:52 ` Daniel Berlin
2001-07-19 9:48 ` Jim Blandy [this message]
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=npwv54uanl.fsf@zwingli.cygnus.com \
--to=jimb@zwingli.cygnus.com \
--cc=dan@cgsoftware.com \
--cc=gdb@sources.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