From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: [commit] Re: [patch 5/7] STT_GNU_IFUNC symbols reader
Date: Mon, 28 Mar 2011 20:32:00 -0000 [thread overview]
Message-ID: <20110328202826.GE26451@host1.jankratochvil.net> (raw)
In-Reply-To: <m3ipv3qe8k.fsf@fleche.redhat.com>
On Mon, 28 Mar 2011 20:41:47 +0200, Tom Tromey wrote:
> Yeah, but I don't like that. It isn't a big issue if you want to keep
> it as-is.
Left it as-is. All the uses of hashtab_obstack_allocate could be reviewed
although it is also no concern in this case IMO.
The hash size 1 gets mapped to the next highest prime 7 which is also high
enough so I have left there 1, also other GDB code is using size 1 there.
Checked in:
http://sourceware.org/ml/gdb-cvs/2011-03/msg00313.html
Thanks,
Jan
prev parent reply other threads:[~2011-03-28 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 21:17 Jan Kratochvil
2011-03-21 21:15 ` Tom Tromey
2011-03-28 14:22 ` Jan Kratochvil
2011-03-28 19:52 ` Tom Tromey
2011-03-28 20:32 ` Jan Kratochvil [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=20110328202826.GE26451@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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