From: Daniel Berlin <dberlin@dberlin.org>
To: Daniel Jacobowitz <drow@mvista.com>
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:38:00 -0000 [thread overview]
Message-ID: <525F4E67-F035-11D6-9C11-000393575BCC@dberlin.org> (raw)
In-Reply-To: <20021104202641.GA7194@nevyn.them.org>
> Not only will they agree, I believe Petr and John had already finished
> doing this.
>
And I did it before them.
> 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.
PS I remember someone mentioning something about not needing to
basically rewrite the dwarf2 reader to do this, though, which is what
"pretty pervasive changes" sounds like. Not that i'm bitter, i just
find it funny. :)
Though i'm aware the retort will be that i did more than necessary
(like mmapping the symbol files, and the ever controversial duplicate
removal).
Jim, you should be able to just rip the pieces from the dwarf2 reader
rewrite i had done, or Petr did, without any trouble.
> [For instance, from Petr's July posting:
> * dwarf2read.c (build_die_ref): New function that builds
> a new die reference if necessary, will search across
> multiple comp units to find the reference.
> (find_die_ref): New function that searches for a die
> reference for a given comp unit.
> (find_cu_header_from_begin_offset): New function that
> searches through a link list of comp unit headers for
> a comp unit that matches the given offset.
> ]
>
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-11-04 20:38 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 [this message]
2002-11-04 12:50 ` Daniel Jacobowitz
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=525F4E67-F035-11D6-9C11-000393575BCC@dberlin.org \
--to=dberlin@dberlin.org \
--cc=ac131313@redhat.com \
--cc=drow@mvista.com \
--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