From: Pedro Alves <palves@redhat.com>
To: Dmitry Antipov <dantipov@nvidia.com>
Cc: gdb@sourceware.org
Subject: Re: Note on choosing string hash functions
Date: Tue, 28 Nov 2017 15:23:00 -0000 [thread overview]
Message-ID: <e3edeb52-675d-a04a-1d0f-4a9bd6981c3e@redhat.com> (raw)
In-Reply-To: <05be76c3-56ff-36bf-ec57-e1339684381d@nvidia.com>
On 11/28/2017 03:13 PM, Dmitry Antipov wrote:
> On 11/28/2017 03:00 PM, Pedro Alves wrote:
>
>> Anyway, this is just a brain dump from a little investigation I did
>> this past
>> weekend, and I think that this area has a lot of scope for
>> improvements, but
>> I won't be able to follow up on any of this myself in the next following
>> weeks at least, with several gdb 8.1 issues on my platе.
>
> Just for the record, I have a brain dump around this area too :-).
> Instead of
> optimizing htab_hash_string itself, we can try to reduce number of calls
> (and
> drop a few calls to strcmp as well if lucky):
Oh, that does sound like a good idea indeed.
Thanks,
Pedro Alves
prev parent reply other threads:[~2017-11-28 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 9:50 Dmitry Antipov
2017-11-17 13:42 ` Pedro Alves
2017-11-22 2:10 ` Pedro Alves
2017-11-22 2:25 ` Pedro Alves
2017-11-28 10:35 ` Dmitry Antipov
2017-11-28 12:00 ` Pedro Alves
2017-11-28 15:13 ` Dmitry Antipov
2017-11-28 15:23 ` Pedro Alves [this message]
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=e3edeb52-675d-a04a-1d0f-4a9bd6981c3e@redhat.com \
--to=palves@redhat.com \
--cc=dantipov@nvidia.com \
--cc=gdb@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