Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: Jim Blandy <jimb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA/dwarf] Allocate abbrevs from a new obstack
Date: Thu, 26 Feb 2004 23:05:00 -0000	[thread overview]
Message-ID: <20040226230515.GB8487@nevyn.them.org> (raw)
In-Reply-To: <16446.29085.601789.628010@localhost.redhat.com>

On Thu, Feb 26, 2004 at 05:22:21PM -0500, Elena Zannoni wrote:
> Jim Blandy writes:
>  > 
>  > Daniel Jacobowitz <drow@false.org> writes:
>  > > Another independent performance optimization from my profiling.  This one is
>  > > good for several percent speedup on mainline.  My original description:
>  > > 
>  > >   - It plugs a huge memory leak.  After loading partial symbols for
>  > >   libc, GDB uses 5.6MB memory without this patch and 1.6MB with it.
>  > >   We weren't emptying the abbrev table.
>  > > 
>  > > [Specifically, we were emptying it after dwarf2_build_psymtabs_hard,
>  > > instead of once each time through the loop.  dwarf2_read_abbrevs then
>  > > zeroed out the allocated, unreferenced pointers.]
>  > > 
>  > >   - I spent a lot of time trying to find alternate data structures that
>  > >   would be more efficient.  The expandable hash table is slower, even if
>  > >   you initially allocate it to the right size.  The splay tree I expected
>  > >   to be quite good in this case, but it isn't either; the overhead is simply
>  > >   too high.  The fixed-size ad-hoc hash table appears to be the best we can
>  > >   do.
>  > > 
>  > > Tested on i686-pc-linux-gnu, no regressions.  OK to commit?
>  > 
>  > Looks great --- please do.
> 
> Jim, there was agreement to not touch these central files until after
> the branch.

Was there?  The closest I saw was an agreement not to merge intercu
support.  This patch is not particularly important, or the other
optimization patch, but they are independent of that.  I would like to
see the duplicate symbols patch reviewed before the branch.

In any case, I won't commit this one until after the branch - which I
think is coming up in about an hour.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2004-02-26 23:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-25  3:55 Daniel Jacobowitz
2004-02-26 22:09 ` Jim Blandy
2004-02-26 22:27   ` Elena Zannoni
2004-02-26 23:05     ` Daniel Jacobowitz [this message]
2004-03-19  0:09   ` Daniel Jacobowitz
2004-03-09 16:58     ` Daniel Jacobowitz

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=20040226230515.GB8487@nevyn.them.org \
    --to=drow@false.org \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jimb@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