From: Ralf Baechle <ralf@oss.sgi.com>
To: Eric Christopher <echristo@redhat.com>
Cc: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>,
"H . J . Lu" <hjl@lucon.org>,
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: Tue, 7 Aug 2001 01:49:10 +0200 [thread overview]
Message-ID: <20010807014910.B22966@bacchus.dhis.org> (raw)
In-Reply-To: <997108890.1773.22.camel@ghostwheel.cygnus.com>; from echristo@redhat.com on Mon, Aug 06, 2001 at 03:41:28PM +0100
On Mon, Aug 06, 2001 at 03:41:28PM +0100, Eric Christopher wrote:
> Hrm. You might be right. I was thinking that would be correct though.
> AFAICT from reading the c++ standard, it doesn't care about the size of
> wchar_t as long as it is large enough to hold the values from the
> supported locales.
>
> Perhaps some c++ expert could help with this a bit? Benjamin is there a
> problem if wchar_t becomes 64-bits?
On 64-bit MIPS ABI compliant machines I see wchar_t defined to __int32_t
which again is int.
Ralf
next prev parent reply other threads:[~2001-08-06 23:50 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 ` Ralf Baechle [this message]
2001-08-06 15:22 ` Changing WCHAR_TYPE from "long int" to "int"? 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=20010807014910.B22966@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=echristo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=hjl@lucon.org \
--cc=ica2_ts@csv.ica.uni-stuttgart.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.