Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] Symbol hashing (for the last time?)
Date: Wed, 10 Jul 2002 19:08:00 -0000	[thread overview]
Message-ID: <15660.58745.329143.773104@localhost.redhat.com> (raw)
In-Reply-To: <20020711005652.GA17895@nevyn.them.org>

Daniel Jacobowitz writes:
 > Here's a patch from last October, dusted off and merged to the current
 > sources.  The only substantial changes were some fixes for ada-lang.c,
 > merged after I wrote the original patch.  I've verified no regressions
 > on i386-linux for GCC (2.95,3.0.4,3.1)/(stabs,dwarf2).
 >

On my plate as well. I think I reviewed a few precursor patches to
this. I have to reread the old threads.

Of course if anybody else has comments, please feel free.

Elena

 
 > This converts the normal symbol table lookups into hash tables.  A few
 > sorts of symbol tables aren't hashed: those produced by mdebugread.c
 > and dstread.c, because they build symbol tables in lots of ad-hoc code,
 > and symbol tables which are actually the arguments to a function
 > (because order matters, or at least comments suggest so).  A next step
 > will be to convert mdebugread.c, delete dstread.c (it's marked for an
 > upcoming obsoletion, isn't it?), and then delete all the complicated
 > binary search code since the only remaining unhashed symtabs will be
 > argument lists, which are small.
 > 
 > This should help performance a bit on large programs.  Ok to commit? 
 > Anyone see any problems with it?
 > 


  reply	other threads:[~2002-07-11  1:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-30  8:28 Daniel Jacobowitz
2002-07-10 18:55 ` Daniel Jacobowitz
2002-07-10 19:08   ` Elena Zannoni [this message]
2002-07-11 10:43   ` Jim Blandy
2002-07-11 12:25     ` Daniel Jacobowitz
2002-07-11 13:12   ` Elena Zannoni
2002-07-11 13:51     ` 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=15660.58745.329143.773104@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=drow@mvista.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