From: Zack Weinberg <zack@codesourcery.com>
To: binutils@sourceware.org
Subject: Re: gas/hash.c: add interface for looking up non-NUL-terminated strings
Date: Mon, 04 Apr 2005 05:33:00 -0000 [thread overview]
Message-ID: <87is33gl7v.fsf@codesourcery.com> (raw)
In-Reply-To: <20050404032129.GH7121@bubble.modra.org> (Alan Modra's message of "Mon, 4 Apr 2005 12:51:29 +0930")
Alan Modra <amodra@bigpond.net.au> writes:
> On Tue, Mar 29, 2005 at 12:00:37PM -0800, Zack Weinberg wrote:
>>
>> The appended patch adds a new interface to gas/hash.c, hash_find_n,
>> with exactly the same semantics as hash_find except that the length of
>> the key is passed in as an argument, and the key is not assumed to be
>> NUL-terminated. This is more convenient when parsing an assembly
>> instruction: one does not need to write a NUL into the line buffer so
>> that hash_find knows where to stop.
>
> Hmm, seems to me that writing a NUL into the line buffer isn't that
> onerous.
I suppose to some extent it's a matter of taste, but having this
interface available allows me to make dramatic simplifications in
tc-arm.c. I should have something to show y'all sometime this week on
that score.
> I'd like to see more justification for this patch, particularly
> since we have too many hash table implementations already in
> binutils. At some stage I'd like to move bfd and gas over to use
> libiberty's hashtab.c, and another interface difference will make
> that task harder.
For what GAS uses hash tables for, I don't think that's a good idea.
libiberty's hashtab.c is extremely generic; you'd have to write
nontrivial amounts of wrapper code, and you'd take a nasty performance
hit. (multiple indirect function calls on every lookup).
cpplib's symtab.c might be a better fit (it can be used independently
from the rest of cpplib) -- and it already has this interface. :)
>> - if (strcmp (p->string, key) == 0)
>> + if (p->string[len] == '\0' && strncmp (p->string, key, len) == 0)
>
> Potential access past the end of p->string. The strncmp must come
> first.
Good point, will correct in my copy.
zw
prev parent reply other threads:[~2005-04-04 5:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 10:49 Zack Weinberg
2005-04-04 3:21 ` Alan Modra
2005-04-04 5:33 ` Zack Weinberg [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=87is33gl7v.fsf@codesourcery.com \
--to=zack@codesourcery.com \
--cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).