https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38308
--- Comment #7 from jerome.h...@planete-sciences.org ---
I know nothing of the inner workings of gcc, but what I can imagine, is that to
check a wchar_t string is easier than a char string, because some encodings may
use variable length multibyte
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38308
--- Comment #6 from Joseph S. Myers ---
*** Bug 93406 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38308
Joseph S. Myers changed:
What|Removed |Added
CC||jerome.hamm@planete-science
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38308
Andrew Pinski changed:
What|Removed |Added
CC||vhaisman at gmail dot com
--- Comment #4
--- Comment #3 from pinskia at gcc dot gnu dot org 2008-11-29 03:12 ---
Confirmed.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Status|UNCON
--- Comment #2 from joseph at codesourcery dot com 2008-11-28 17:26 ---
Subject: Re: -Wformat does not work for wide strings
In view of the removal of c4x support I don't now think any patch for this
needs to address the format of STRING_CSTs for non-8-bit target bytes.
But it shoul
--- Comment #1 from pinskia at gcc dot gnu dot org 2008-11-28 16:58 ---
A patch was posted a while back:
http://gcc.gnu.org/ml/gcc-patches/2001-12/msg01579.html
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38308
