From: Andrew Cagney <ac131313@ges.redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Hilfinger@otisco.mckusick.com, carlton@math.stanford.edu,
gdb-patches@sources.redhat.com, aidan@velvet.net,
jimb@redhat.com, ezannoni@redhat.com
Subject: Re: [RFA] delete BLOCK_SHOULD_SORT
Date: Thu, 19 Sep 2002 08:04:00 -0000 [thread overview]
Message-ID: <3D89E777.9060500@ges.redhat.com> (raw)
In-Reply-To: <20020919132923.GA16924@nevyn.them.org>
> On Thu, Sep 19, 2002 at 01:04:10AM -0700, Paul N. Hilfinger wrote:
> Paul, David,
>
> I believe that the right thing to do with this code is actually to
> tranform it into calls to search_symbols and let that handle the
> details. We have a regexp symbol matching interface... and it's not
> significantly slower, given that almost no symbol tables are sorted now
> anyway.
Yes.
If someone comes forward with evidence demonstrating that the lookup is
a bottle neck, then the symbol database internals can be adjusted to
address the performance problem. I don't think core GDB (ignoring
!@*$(&*#@&$* stabs) should be worried about the table sort order.
David,
Watch out for things like info symbols. From memory their behavior is
affected by this - something DanielJ and ElenaZ hit problems with when
playing with this before.
Andrew
next prev parent reply other threads:[~2002-09-19 15:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-18 15:16 David Carlton
2002-09-18 19:25 ` Daniel Jacobowitz
2002-09-19 1:04 ` Paul N. Hilfinger
2002-09-19 6:29 ` Daniel Jacobowitz
2002-09-19 8:04 ` Andrew Cagney [this message]
2002-09-19 9:29 ` David Carlton
2002-09-22 16:02 ` Jim Blandy
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=3D89E777.9060500@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=Hilfinger@otisco.mckusick.com \
--cc=aidan@velvet.net \
--cc=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--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