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: PATCH[BIB}: Removing the arg_index field from cpp_hashnode

From: Zack Weinberg <zack at codesourcery dot com>
To: Richard Henderson <rth at redhat dot com>,Zack Weinberg <zack at codesourcery dot com>,Per Bothner <per at bothner dot com>, gcc-patches at gcc dot gnu dot org
Date: Fri, 6 Dec 2002 15:34:55 -0800
Subject: Re: PATCH[BIB}: Removing the arg_index field from cpp_hashnode
References: <3DF107B3.6020706@bothner.com> <20021206230527.GH15574@redhat.com> <20021206231750.GA28830@egil.codesourcery.com> <20021206232757.GJ15574@redhat.com>

On Fri, Dec 06, 2002 at 03:27:57PM -0800, Richard Henderson wrote:
> On Fri, Dec 06, 2002 at 03:17:50PM -0800, Zack Weinberg wrote:
> > Bother.  Suggestions?  This whole exercise is pointless if all we do
> > is turn actively used bytes into padding.
> 
> With the structure in question, you moved padding from one place
> to another, didn't make things worse.  What's the larger context here?

We were hoping to make it smaller.  There's now enough tail padding
that it *could* be used for the next field, if that were permitted.

zw

Follow-Ups:
- Re: PATCH[BIB}: Removing the arg_index field from cpp_hashnode
  - From: Per Bothner

References:
- PATCH[BIB}: Removing the arg_index field from cpp_hashnode
  - From: Per Bothner
- Re: PATCH[BIB}: Removing the arg_index field from cpp_hashnode
  - From: Richard Henderson
- Re: PATCH[BIB}: Removing the arg_index field from cpp_hashnode
  - From: Zack Weinberg
- Re: PATCH[BIB}: Removing the arg_index field from cpp_hashnode
  - From: Richard Henderson

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