This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: PATCH: use hashtab for pseudo op table

From: Richard Henderson <rth at redhat dot com>
To: Zack Weinberg <zack at codesourcery dot com>
Cc: Dave Korn <dave dot korn at artimi dot com>, "'Nick Clifton'" <nickc at redhat dot com>, "'Alan Modra'" <amodra at bigpond dot net dot au>, "'Ben Elliston'" <bje at au1 dot ibm dot com>, binutils at sources dot redhat dot com
Date: Thu, 5 May 2005 23:20:10 -0700
Subject: Re: PATCH: use hashtab for pseudo op table
References: <SERRANOIA3EEmYDKFJ200000245@SERRANO.CAM.ARTIMI.COM> <87fyx1cxfl.fsf@codesourcery.com> <20050505200909.GA31889@redhat.com> <87vf5wev64.fsf@codesourcery.com>

On Thu, May 05, 2005 at 11:16:19PM -0700, Zack Weinberg wrote:
> Won't horrible things happen when it tries to resize the table, if you
> do that?

No, there are two hash functions.  The one you give at hash table 
creation knows about the object stored in.  That's why you have to
call the "*_with_hash" function directly.

We do this in several places in gcc itself.

r~

Follow-Ups:
- Re: PATCH: use hashtab for pseudo op table
  - From: Zack Weinberg

References:
- RE: PATCH: use hashtab for pseudo op table
  - From: Dave Korn
- Re: PATCH: use hashtab for pseudo op table
  - From: Zack Weinberg
- Re: PATCH: use hashtab for pseudo op table
  - From: Richard Henderson
- Re: PATCH: use hashtab for pseudo op table
  - From: Zack Weinberg

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]