This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC 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: [RFC] [PATCH] Move cpplib out of the gcc directory

From: Paolo Bonzini <bonzini at gnu dot org>
To: DJ Delorie <dj at redhat dot com>
Cc: gcc-patches at gcc dot gnu dot org
Date: Wed, 19 May 2004 01:00:40 +0200
Subject: Re: [RFC] [PATCH] Move cpplib out of the gcc directory
References: <40AA8E23.9060609@gnu.org> <200405182251.i4IMp74V002191@greed.delorie.com>

Moving things into libiberty should not be taken lightly, as the
change rules for libiberty are more strict than for gcc (backwards
compatibility and multi-project use).

hashtable.c is not changing at a very fast pace. After 3 years, it is at revision 1.16. I don't think that backwards compatibility will be a hindrance.

I would suggest not making the
above change without a definite reason.

My reason was to be that a generic fast hash table for strings seems to belong in libiberty more than in cpplib.

(Ian: renaming the file was useless work, it is already quite late here. I'd also thought of hashstr.c).

Paolo

Follow-Ups:
- Re: [RFC] [PATCH] Move cpplib out of the gcc directory
  - From: DJ Delorie

References:
- [RFC] [PATCH] Move cpplib out of the gcc directory
  - From: Paolo Bonzini
- Re: [RFC] [PATCH] Move cpplib out of the gcc directory
  - From: DJ Delorie

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