From: "H . J . Lu" <hjl@lucon.org>
To: Eric Christopher <echristo@redhat.com>
Cc: 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 08:22:19 -0700 [thread overview]
Message-ID: <20010806082219.A15666@lucon.org> (raw)
In-Reply-To: <997107178.1253.7.camel@ghostwheel.cygnus.com>; from echristo@redhat.com on Mon, Aug 06, 2001 at 03:12:56PM +0100
On Mon, Aug 06, 2001 at 03:12:56PM +0100, Eric Christopher wrote:
>
> > I am working on will be the first gcc 3.x for Linux/mips. So there
> > shouldn't be any problems. Am I right?
>
> I _think_ you are ok doing this.
>
> I just noticed from your patch that you set the size to 32-bits. Please
> set it to BITS_PER_WORD.
>
BITS_PER_WORD is not right. That is what prompted me to make the
change. There are a few things about the MIPS ABI:
1. We do follow the ABI part.
2. We care much less about the API part. That is in the section 6 where
wchar_t is defined.
3. On mips, sizeof (int) == sizeof (long int).
But BITS_PER_WORD can be 32 or 64, depending on TARGET_LONG64. As for
WCHAR_TYPE, it should be `int' regardless of TARGET_LONG64. For most of
the 64bit Linux targets, sizeof (int) should be 32bit. That means
WCHAR_TYPE_SIZE should be 32 for mips.
H.J.
prev parent reply other threads:[~2001-08-06 15: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 ` Changing WCHAR_TYPE from "long int" to "int"? Ralf Baechle
2001-08-06 16:29 ` 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 [this message]
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=20010806082219.A15666@lucon.org \
--to=hjl@lucon.org \
--cc=echristo@redhat.com \
--cc=gcc@gcc.gnu.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