| To: | "H . J . Lu" <hjl@lucon.org> |
|---|---|
| Subject: | Re: Changing WCHAR_TYPE from "long int" to "int"? |
| From: | Gabriel Dos Reis <gdr@codesourcery.com> |
| Date: | 05 Aug 2001 19:06:14 +0200 |
| Cc: | 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: | "H . J . Lu"'s message of "Sun, 5 Aug 2001 09:48:06 -0700" |
| Organization: | CodeSourcery, LLC |
| References: | <20010805094806.A3146@lucon.org> |
| Sender: | owner-linux-mips@oss.sgi.com |
"H . J . Lu" <hjl@lucon.org> writes: | 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? Normally, wchar_t is a keyword in C++ (as opposed to typedef in C). So at first sight, I would think there should be no problem with changing WCHAR_TYPE. But then, I may be missing some subtile ABI point. -- Gaby |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Changing WCHAR_TYPE from "long int" to "int"?, H . J . Lu |
|---|---|
| Next by Date: | Qube2 gcc 2.7.2 compiler error, John Heil |
| Previous by Thread: | Changing WCHAR_TYPE from "long int" to "int"?, H . J . Lu |
| Next by Thread: | Re: Changing WCHAR_TYPE from "long int" to "int"?, Eric Christopher |
| Indexes: | [Date] [Thread] [Top] [All Lists] |