http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52539
--- Comment #17 from Tobias Burnus <burnus at gcc dot gnu.org> --- (In reply to Jerry DeLisle from comment #16) > A user should not have to artificially construct a string to accommodate > endianess. In principle, the user doesn't have to do so. UTF-8 itself is agnostic to the endianness of the system. The endian issue only comes up in the source code. To solve this, we have to handle UTF-8 when reading the source code. libcpp, which we use for the input, handles multiple encodings. We should use find out how to use this - and use it for 4_'strings'.
