This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: thoughts on martin's proposed patch for GCC and UTF-8
ASCII-only name mangling ought to achieve that. Could you
please explain why you think it will not?
* This will work, but it's unfriendly for non-English writers,
Making .s files "friendly" for non-ASCII scripts
is a very low-priority goal. There are, or have been, some
assemblers which required all strings to be expressed with .byte.
So what? Above all, we have to do the right thing for compiler
*users*; making .s files look nice has to come second.
Even when not converting, GCC needs to know the input encoding if it's
an unsafe one like Shift-JIS or ISO-2022-JP (``unsafe'' meaning ``some
multibyte chars contain ASCII bytes'')
Yes, that's true. However, we can arrange for GCC to do the right
thing without knowing the actual encoding, when the real encoding is a
safe one--as long as GCC does not think you have specified an unsafe
encoding.