[Bug c/41041] Documentation: -fwide-exec-charset defaults to UCS-4/UCS-2, not UTF-32/UTF-16
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41041 Samuel Thibault changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #9 from Samuel Thibault --- It seems it indeed is by default a UTF encoding rather than a UCS encoding: $ LANG= gcc -fshort-wchar test.c -o test $ LANG= gcc -fshort-wchar test.c -o test -fwide-exec-charset=UTF-16LE $ LANG= gcc -fshort-wchar test.c -o test -fwide-exec-charset=UCS-2LE test.c: In function `main': test.c:7:27: error: converting to execution character set: Invalid or incomplete multibyte or wide character 7 | wchar_t s[] = L"𝄞"; | ^ Now there is indeed the question of the BOM. Ideally the text could mention all of UTF-32LE, UTF-32BE, UTF-16LE, UTF-16BE, but not sure it's really worth it.
[Bug modula2/113749] [14 Regression] m2 enabled build times out on i686-gnu (GNU Hurd)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113749 --- Comment #3 from Samuel Thibault --- I don't think it is a regression. We noticed it only recently in Debian only because the configuration files got bogus. See for instance https://buildd.debian.org/status/fetch.php?pkg=gcc-13&arch=hurd-i386&ver=13.2.0-10&stamp=1705711375&raw= which fails the same: m2/boot-bin/mc --olang=c++ --h-file-prefix=G -I../../src/gcc/m2/gm2-libs -I../../src/gcc/m2/gm2-compiler -I../../src/gcc/m2/gm2-libiberty -I E: Build killed with signal TERM after 180 minutes of inactivity And we can trace it back to this commit in debian: commit ac0e3d134553e01c04b6a1b7f9c855fcb747dd6f Author: Matthias Klose Date: Tue Oct 8 10:34:25 2019 +0200 * Disable gm2 on hurd-i386, mc hangs there (Samuel Thibault). Closes: #940600. That being said, it'd still be good to fix it, sure :)
