Re: Incompatible compiler option fexec-charset

[Wolfgang Lux]

Richard Frith-Macdonald wrote:

>> In that case I don't understand why you want to add -finput-charset=UTF-8 to 
>> the compiler options. This flag changes the interpretation of the *source* 
>> file.
> 
> That's only used while compiling the base library ... because the base 
> library source is guaranteed to be UTF-8 (as David pointed out, that's the 
> *sane* way to do things), and we therefore don't want people building the 
> base library with an environment which would cause string literals in the 
> source to be interpreted as any other characterset.  At present this is 
> unnecessary (as we actually only use ascii literals), but it makes the code 
> future-proof.

Okay, that makes sense to me (as I said, I'm sometimes a bit dumb :-)

>> In fact, I'd say if the compiler ever succeeds compiling the test example 
>> with -finput-charset=UTF-8 then the compiler either ignores the option 
>> altogether or it is broken since the ISO-Latin 1 pound character is an 
>> invalid character in a UTF-8 encoded file.
> 
> 
> The compiler is never asked to build the config test as UTF-8 ... the whole 
> point of the testy is to check that the compiler produces UTF-8 binaries when 
> given non-UTF-8 source.

Yes, I just noticed after posting that it's using -finput-charset=ISO-8859-1 
and not -finput-charset=UTF-8.

Wolfgang