http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56086
Jason Merrill changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56086
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org,
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56086
--- Comment #4 from joseph at codesourcery dot com 2013-01-28 03:43:31 UTC ---
For C, char16_t and char32_t are typedefs in (a header provided
by the C library, not by GCC), *not* built-in types, and __STDC_UTF_16__
is a built-in macro.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56086
--- Comment #3 from Roger Jarrett 2013-01-27
16:13:48 UTC ---
The macro __STDC_UTF_16__ is being used to guard the following typedef
typedef char16_t CHAR16_T;
compiling the program (attached program t2.c)
typedef char16_t fred;
int m
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56086
--- Comment #2 from Roger Jarrett 2013-01-27
16:12:09 UTC ---
Created attachment 29285
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29285
example program to compile
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56086
--- Comment #1 from joseph at codesourcery dot com 2013-01-23 20:47:49 UTC ---
Why do you think this is a bug? GCC meets the semantics of that macro
(that char16_t values are UTF-16 encoded), and gnu99 mode enables u""
strings.
