Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Hilfinger@adacore.com
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Extend hashed symbol dictionaries to work with Ada
Date: Wed, 06 Oct 2010 22:43:00 -0000	[thread overview]
Message-ID: <m3wrpv0wob.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201010050820.o958Kf42002588@syracuse.mckusick.com> (Paul	Hilfinger's message of "Tue, 5 Oct 2010 01:20:41 -0700")

>>>>> "Paul" == Paul Hilfinger <hilfingr@syracuse.mckusick.com> writes:

Paul> This patch allows Ada to speed up symbol lookup by using the facilities
Paul> in dictionary.[ch] for hashed lookups.

Paul> Because this patch touches on a hashing algorithm used by other
Paul> languages, I took the precaution of doing a speed test on a list of
Paul> about 12000 identifiers (repeatedly inserting all of them into a table
Paul> and then doing a lookup on a million names at random, thus testing the
Paul> speed of the hashing algorithm and how well it distributed names).

Thanks for looking at this.

Paul> +full_match (const char* sym_name, const char* search_name)

I noticed a few spots in the patch with "char* something" instead of
"char *something".

Paul> +	case '$': case '.': case 'X': case '(':

I personally think it is clearer to put each case on a separate line,
but I don't insist on it.

This is ok with the "char *" spacing thing fixed.

Tom


  reply	other threads:[~2010-10-06 22:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05  8:20 Paul Hilfinger
2010-10-06 22:43 ` Tom Tromey [this message]
2010-10-06 22:53   ` Tom Tromey
2010-10-07  3:31     ` Paul Hilfinger
2010-10-07  7:17     ` [commit] " Paul Hilfinger
2010-10-07  8:44     ` [commit] Correct dict_hash to our most recent version Paul Hilfinger, :
2010-10-08 22:59       ` Tom Tromey
2010-10-07  3:29   ` [RFA] Extend hashed symbol dictionaries to work with Ada Paul Hilfinger
2010-10-06 23:18 ` Joel Brobecker
2010-10-06 23:59 ` Doug Evans
2010-10-07  6:29   ` Paul Hilfinger

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=m3wrpv0wob.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=Hilfinger@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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