On 8/12/19 4:24 PM, Thiago Macieira wrote:
>
> This has broken down in recent decades because Clang and GCC do a pass-through
> from the source charset to the narrow execution charset. So you can't get the
> same for non-ASCII. The following source if encoded in Latin1:
>
> char str[] = "é";
>
> will not behave properly under UTF-8 execution charset at runtime. I don't
> know if -finput-charset=latin1 makes a difference.

Use of -finput-charset=latin1 does suffice for gcc to DTRT.

It is a little disappointing that no warning is issued, even when
-finput-charset=utf-8 is specified.

Tom.

>
> MSVC without /utf-8, on the other hand, has the traditional interpretation.
>