From: Alan Modra <amodra@bigpond.net.au>
To: Nick Clifton <nickc@redhat.com>
Cc: Zack Weinberg <zack@codesourcery.com>,
Ben Elliston <bje@au1.ibm.com>,
binutils@sources.redhat.com
Subject: Re: PATCH: use hashtab for pseudo op table
Date: Thu, 05 May 2005 10:57:00 -0000 [thread overview]
Message-ID: <20050505104821.GA32657@bubble.grove.modra.org> (raw)
In-Reply-To: <4279EDEB.1060601@redhat.com>
On Thu, May 05, 2005 at 10:56:59AM +0100, Nick Clifton wrote:
> Hi Ben, Hi Zack,
>
> > Zack Weinberg wrote:
> >I do not think replacing gas/hash.c with hashtab.c is a good idea, for
> >reasons laid out (somewhat cursorily) in
> ><http://sources.redhat.com/ml/binutils/2005-04/msg00056.html>. I can
> >expand if anyone wants to hear it.
>
> I agree - Ben, what is your motivation for removing hash.c ?
Probably because I was talking to Ben a week or so ago, and mentioned
that it's silly that we have so many hash table implementations. We
have libiberty/hashtab.c, bfd/hash.c, and gas/hash.c. Some of bfd
already uses libiberty/hashtab.c due to it's rather nice auto-resize,
and more of bfd should. ie. I see libiberty/hashtab.c as the way of
the future.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2005-05-05 10:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 8:21 Ben Elliston
2005-04-29 8:52 ` Zack Weinberg
2005-05-05 10:00 ` Nick Clifton
2005-05-05 10:57 ` Alan Modra [this message]
2005-05-05 11:46 ` Nick Clifton
2005-05-05 12:37 ` Alan Modra
2005-05-05 17:14 ` Zack Weinberg
2005-05-05 17:58 ` Dave Korn
2005-05-05 18:59 ` Zack Weinberg
2005-05-05 19:44 ` DJ Delorie
2005-05-05 20:10 ` Richard Henderson
2005-05-06 6:17 ` Zack Weinberg
2005-05-06 6:44 ` Richard Henderson
2005-05-06 7:36 ` Zack Weinberg
2005-05-05 19:20 ` DJ Delorie
2005-05-17 13:19 ` Nick Clifton
2005-05-05 15:24 ` H. J. Lu
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=20050505104821.GA32657@bubble.grove.modra.org \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.redhat.com \
--cc=bje@au1.ibm.com \
--cc=nickc@redhat.com \
--cc=zack@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).