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: Reorder some tree codes

From: Nathan Sidwell <nathan at codesourcery dot com>
To: Zack Weinberg <zack at codesourcery dot com>
Cc: Mark Mitchell <mark at codesourcery dot com>, Wolfgang Bangerth <bangerth at ices dot utexas dot edu>, gcc-patches at gcc dot gnu dot org, nathan at gcc dot gnu dot org
Date: Wed, 22 Dec 2004 18:55:14 +0000
Subject: Re: Reorder some tree codes
Organization: CodeSourcery LLC
References: <Pine.LNX.4.60.0412201115240.9847@terra.ices.utexas.edu> <41C71D42.2080909@codesourcery.com> <41C85879.6040902@codesourcery.com> <87brcniikh.fsf@codesourcery.com>

Zack Weinberg wrote:

Reducing the width of IN_RANGE from unsigned HOST_WIDE_INT to unsigned
makes me nervous.  Why did you need to do that?


I had thought that IN_RANGE was no longer used anywhere, but clearly
I had a grep malfunction.  I've now found one other use in java/lex.c, where
the value is a unicode_t type.  I was worried about lame sign extensions
confusing things where HOST_WIDE_INT was wider than plain unsigned.

nathan

--
Nathan Sidwell    ::   http://www.codesourcery.com   ::     CodeSourcery LLC
nathan@codesourcery.com    ::     http://www.planetfall.pwp.blueyonder.co.uk

Follow-Ups:
- Re: Reorder some tree codes
  - From: Mark Mitchell

References:
- Re: Reorder some tree codes
  - From: Wolfgang Bangerth
- Re: Reorder some tree codes
  - From: Mark Mitchell
- Re: Reorder some tree codes
  - From: Nathan Sidwell
- Re: Reorder some tree codes
  - From: Zack Weinberg

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