From: Michael Snyder <msnyder@cygnus.com>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC]: New dwarf2 reader
Date: Fri, 29 Jun 2001 14:05:00 -0000 [thread overview]
Message-ID: <3B3CED9B.8CAC8FB1@cygnus.com> (raw)
In-Reply-To: <87pubnluqa.fsf@cgsoftware.com>
Daniel Berlin wrote:
>
> Still a work in progress, however, i'm only bugfixing now, as i'm
> happy with memory usage, etc.
>
> Changes:
> 1.
> This has an improved implementation of removing duplicates. It's done
> basically the same way gcc does it, which is to actually just go all out and md5
> checksum the attributes of dies. Conservatively, of course.
> Currently, this means that duplicate things with different offsets for their
> types, siblings, etc, don't get eliminated.
> I'll improve this in a bit (We'll ignore the sibling attribute for
> checksum purposes, and a few other minor twiddles.)
>
> You'd think that the fact that the relative placement inside the
> section mattering would stop us from eliminating most duplicates.
> You'd be very wrong.
>
> GCC, by deferring output a lot, tends to end up outputting things in
> the same order.
>
> We are now down to 21 meg of memory to debug gdb, with all symbols
> fully read in.
> Down from 80.
>
> STABS takes 22 or 24, I forget which.
Daniel, this is a very promising development. Have you done any
timing checks? How long does it take to load all those symbols
and remove duplicates, compared to the old code?
next prev parent reply other threads:[~2001-06-29 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-28 22:29 Daniel Berlin
2001-06-28 23:35 ` Andrew Cagney
2001-06-29 8:42 ` Andrew Cagney
2001-06-29 9:03 ` Daniel Berlin
2001-06-29 14:05 ` Michael Snyder [this message]
2001-06-29 19:34 ` Daniel Berlin
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=3B3CED9B.8CAC8FB1@cygnus.com \
--to=msnyder@cygnus.com \
--cc=dan@cgsoftware.com \
--cc=gdb-patches@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