Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Andreas Jaeger <aj@suse.de>
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>
Subject: Re: Changing WCHAR_TYPE from "long int" to "int"?
Date: Mon, 6 Aug 2001 18:20:50 +0200	[thread overview]
Message-ID: <20010806182050.A21142@bacchus.dhis.org> (raw)
In-Reply-To: <hoofptjy6k.fsf@gee.suse.de>; from aj@suse.de on Mon, Aug 06, 2001 at 12:10:59PM +0200

On Mon, Aug 06, 2001 at 12:10:59PM +0200, Andreas Jaeger 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?

It's defined as a "long", not "long int" so we're obviously off by a tiny
bit.

H.J. - why did you want to change this type anyway?  "long int" and "int"
both have the same size and signedness so there isn't any incompatibility
anyway?

  Ralf

  parent reply	other threads:[~2001-08-06 16:22 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-05 16:48 Changing WCHAR_TYPE from "long int" to "int"? H . J . Lu
2001-08-05 17:06 ` Gabriel Dos Reis
2001-08-06  9:59 ` Ralf Baechle
2001-08-06 10:10   ` Andreas Jaeger
2001-08-06 14:27     ` Eric Christopher
2001-08-06 16:28       ` Ralf Baechle
2001-08-07 11:52         ` MIPS ABI (was: Changing WCHAR_TYPE from "long int" to "int"?) Paul Kasper
2001-08-07 12:31           ` Ralf Baechle
2001-08-07 16:07           ` H . J . Lu
2001-08-06 16:20     ` Ralf Baechle [this message]
2001-08-06 16:29       ` Changing WCHAR_TYPE from "long int" to "int"? H . J . Lu
2001-08-06 17:04       ` Gabriel Dos_Reis
2001-08-06 17:25         ` Ralf Baechle
2001-08-06 14:12 ` Eric Christopher
2001-08-06 14:40   ` Thiemo Seufer
2001-08-06 14:41     ` Eric Christopher
2001-08-06 15:29       ` H . J . Lu
2001-08-06 15:33         ` Eric Christopher
2001-08-06 15:39           ` H . J . Lu
2001-08-06 16:23             ` Eric Christopher
2001-08-07  3:56             ` cross-mipsel-linux-ld --prefix library path Bradley D. LaRonde
2001-08-07  3:56               ` Bradley D. LaRonde
2001-08-07  7:40               ` Geert Uytterhoeven
2001-08-07 14:10                 ` Bradley D. LaRonde
2001-08-07 14:10                   ` Bradley D. LaRonde
2001-08-07 14:10               ` Maciej W. Rozycki
2001-08-07 14:14                 ` Bradley D. LaRonde
2001-08-07 14:14                   ` Bradley D. LaRonde
2001-08-07 14:36                   ` Maciej W. Rozycki
2001-08-07 14:42               ` Steve Langasek
2001-08-07 14:42                 ` Steve Langasek
2001-08-07 15:25                 ` Bradley D. LaRonde
2001-08-07 15:25                   ` Bradley D. LaRonde
2001-08-07 19:27                   ` Steve Langasek
2001-08-07 19:27                     ` Steve Langasek
2001-08-06 23:49       ` Changing WCHAR_TYPE from "long int" to "int"? Ralf Baechle
2001-08-06 15:22   ` H . J . Lu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010806182050.A21142@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=aj@suse.de \
    --cc=echristo@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hjl@lucon.org \
    --cc=libc-alpha@sourceware.cygnus.com \
    --cc=linux-mips@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox