From: Daniel Jacobowitz <drow@mvista.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: Jim Blandy <jimb@redhat.com>, John Wolfe <jlw@caldera.com>,
Andrew Cagney <ac131313@redhat.com>,
gdb@sources.redhat.com
Subject: Re: Petr Sorfa's Dwarf 2 changes
Date: Mon, 04 Nov 2002 12:50:00 -0000 [thread overview]
Message-ID: <20021104204549.GA8159@nevyn.them.org> (raw)
In-Reply-To: <525F4E67-F035-11D6-9C11-000393575BCC@dberlin.org>
On Mon, Nov 04, 2002 at 03:38:05PM -0500, Daniel Berlin wrote:
> >Not only will they agree, I believe Petr and John had already finished
> >doing this.
>
> >
> And I did it before them.
Yes, sorry. I still have code from you, posted to gdb-patches in July
2001, which does this. I merged it most of the way forward to CVS a
couple of months later and ran out of time to finish the job.
> > Doubtless there's still some room for improvement, but the
> >functionality is there... John, do you have that merged dwarf2read
> >available?
> If they don't, you should be able to find mine in the archives.
> Unless i'm misremembering Petr's, it keeps all the CU's around all the
> time.
> One thing I did was to make it so you could throw away CU's at will,
> and it would just reread them if/when necessary (IE it would just keep
> the last 10 used CU's or something as a cache). Cuts down on memory
> usage significantly with almost no loss in speed.
Exactly what I was trying to remember :)
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-11-04 20:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-23 10:39 Jim Blandy
2002-10-23 11:48 ` Andrew Cagney
2002-11-04 12:21 ` Jim Blandy
2002-11-04 12:25 ` Daniel Jacobowitz
2002-11-04 12:38 ` Daniel Berlin
2002-11-04 12:50 ` Daniel Jacobowitz [this message]
2002-11-05 9:20 ` Jim Blandy
2002-11-05 9:18 ` Jim Blandy
2002-10-23 11:37 John Wolfe
2002-11-06 7:34 John Wolfe
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=20021104204549.GA8159@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=dberlin@dberlin.org \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=jlw@caldera.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