This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: MULTIBYTE_CHARS in c-lex.c and cp/lex.c
- To: Gavin Romig-Koch <gavin@cygnus.com>
- Subject: Re: MULTIBYTE_CHARS in c-lex.c and cp/lex.c
- From: Dave Brolley <brolley@cygnus.com>
- Date: Tue, 31 Aug 1999 17:26:06 -0400
- CC: gcc@gcc.gnu.org
- Organization: Cygnus Solutions Canada Ltd
- References: <m11Lv4R-000s9vC@cetus.cygnus.com>
Gavin Romig-Koch wrote:
> There is a undef at the top of c-lex.c that turns off MULTIBYTE_CHARS
> if CROSS_COMPILE is set. There is not a similar undef at the top
> of cp/lex.c. Can anybody shed light on why the difference?
>
> Is it because cp/lex.c is always built with gcc, while c-lex.c might
> be built with some other compiler?
The one in c-lex.c should probably be removed. The rationale for it being
there is that the compiler can only recognize and convert multibyte
characters using information provided by the host locale, which may not
make any sense for the target when cross compiling. However, we have
support for several pseudo-locales (C-JIS, C-SJIS, C-EUCJP) which could
be useful in a cross compiler and other host-locale character sets may
also be valid on the target of a cross compiler. So I say, leave it
enabled for cross compilers as well.
Dave