linux-mips
[Top] [All Lists]

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

To: Ralf Baechle <ralf@oss.sgi.com>
Subject: Re: Changing WCHAR_TYPE from "long int" to "int"?
From: Andreas Jaeger <aj@suse.de>
Date: Mon, 06 Aug 2001 12:10:59 +0200
Cc: "H . J . Lu" <hjl@lucon.org>, Eric Christopher <echristo@redhat.com>, gcc@gcc.gnu.org, linux-mips@oss.sgi.com, GNU C Library <libc-alpha@sourceware.cygnus.com>
In-reply-to: <20010806115913.B17179@bacchus.dhis.org> (Ralf Baechle's message of "Mon, 6 Aug 2001 11:59:13 +0200")
Mail-copies-to: never
References: <20010805094806.A3146@lucon.org> <20010806115913.B17179@bacchus.dhis.org>
Sender: owner-linux-mips@oss.sgi.com
User-agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.1 (Cuyahoga Valley)
Ralf Baechle <ralf@oss.sgi.com> writes:

> On Sun, Aug 05, 2001 at 09:48:06AM -0700, H . J . Lu wrote:
>
>> I am working with Eric to clean up the Linux/mips configuration in
>> gcc 3.x. I'd like to change WCHAR_TYPE from "long int" to "int". They
>> are the same on Linux/mips. There won't be any run-time problems. I am
>> wondering if there are any compatibility problems at the compile time
>> at the source and binary level. For one thing, __WCHAR_TYPE__ will be
>> changed from "long int" to "int". The only thing I can think of is
>> the C++ libraries. But gcc 3.x doesn't work on Linux/mips. The one
>> I am working on will be the first gcc 3.x for Linux/mips. So there
>> shouldn't be any problems. Am I right?
>
> The MIPS ABI defines wchar_t to long.  So please go ahead and make the
> change.

I'm confused.  The ABI defines it to be long - and he should change it
nevertheless?

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

Attachment: pgpDlRmJGna3o.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>