From: David Carlton <carlton@math.stanford.edu>
To: Hilfinger@otisco.mckusick.com
Cc: 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 09:29:00 -0000 [thread overview]
Message-ID: <ro1r8fqvt95.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <200209190804.BAA27599@otisco.McKusick.COM>
On Thu, 19 Sep 2002 01:04:10 -0700, "Paul N. Hilfinger" <hilfingr@otisco.mckusick.com> said:
> OK; let me explain what Ada is up to in the various places it does
> symbol lookup, and you can decide if we (ahem) need a conversation
> on this (vis-a-vis this thread or the other "dictionary" threads),
> or if our needs introduce no new requirements.
...
> The second pattern, however, can benefit for sorted blocks in an
> obvious way--- hence the ada-lang.c code you mentioned in an earlier
> message---but doesn't need them. That is, we take advantage of
> BLOCK_SHOULD_SORT when possible. I don't have measurements of the
> impact of not having it.
I see; thanks for the explanation. Then I agree with Daniel: it
should probably be converted to search_symbols, and removing
BLOCK_SHOULD_SORT won't hurt you: the performance gains that you had
been getting were already lost in the earlier conversion from sorted
lists to hashtables, unless the debugging info happens to be in ECOFF
format. So the only question is whether or not I slipped up when
converting those loops to ALL_BLOCK_SYMBOLS.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2002-09-19 16:29 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
2002-09-19 9:29 ` David Carlton [this message]
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=ro1r8fqvt95.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=Hilfinger@otisco.mckusick.com \
--cc=aidan@velvet.net \
--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