This is the mail archive of the gcc@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]

Re: Changing WCHAR_TYPE from "long int" to "int"?

To: "H . J . Lu" <hjl at lucon dot org>
Subject: Re: Changing WCHAR_TYPE from "long int" to "int"?
From: Eric Christopher <echristo at redhat dot com>
Date: 06 Aug 2001 16:33:54 +0100
Cc: Thiemo Seufer <ica2_ts at csv dot ica dot uni-stuttgart dot de>, gcc at gcc dot gnu dot org, linux-mips at oss dot sgi dot com, GNU C Library <libc-alpha at sourceware dot cygnus dot com>
References: <20010806164000.E400@rembrandt.csv.ica.uni-stuttgart.de><997108890.1773.22.camel@ghostwheel.cygnus.com> <20010806082904.C15666@lucon.org>


> Yes. Gcc won't even compile since cpp uses MAX_WCHAR_TYPE_SIZE, which
> is defined as WCHAR_TYPE_SIZE and has be to a constant. But mips'
> BITS_PER_WORD is not avaiable for cpp. Besides, we use 32bit wchar_t
> on most of the 64bit Linux targets. Why do we want to use 64 for
> mips64? Check out WCHAR_TYPE_SIZE on ia64 and alpha, which are all
> 64bit Linux targets.
> 

Right.  alpha doesn't define WCHAR_TYPE_SIZE, ia64 seems to do what you
want...

-eric


-- 
Look out behind you!

Follow-Ups:
- Re: Changing WCHAR_TYPE from "long int" to "int"?
  - From: H . J . Lu

References:
- Re: Changing WCHAR_TYPE from "long int" to "int"?
  - From: Thiemo Seufer
- Re: Changing WCHAR_TYPE from "long int" to "int"?
  - From: Eric Christopher
- Re: Changing WCHAR_TYPE from "long int" to "int"?
  - From: H . J . Lu

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