http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53683
--- Comment #8 from Jonathan Wakely ---
Because your program is ill-formed, and not supposed to compile, so what you
reported is not a bug.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53683
--- Comment #7 from Rui Maciel ---
Why is this bug marked as RESOLVED INVALID ?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53683
--- Comment #6 from Jonathan Wakely ---
We also have but it needs a lot of work to
re-use.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53683
--- Comment #5 from Jonathan Wakely ---
(In reply to Ed Smith-Rowland from comment #4)
> It looks like libcpp/charset.c might have a lot of the guts that could help
> with the implementation of codecvt_utf8, etc.
>
> Maybe we could either get lib
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53683
Ed Smith-Rowland <3dw4rd at verizon dot net> changed:
What|Removed |Added
CC||3dw4rd at ve
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53683
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53683
--- Comment #2 from Rui Maciel 2012-06-15
13:08:01 UTC ---
(In reply to comment #1)
> (In reply to comment #0)
> > If, in the test program, std::u16string is replaced with std::u32string, the
> > program is successfully compiled.
>
> That's surp
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53683
Jonathan Wakely changed:
What|Removed |Added
Component|c++ |libstdc++
--- Comment #1 from Jonathan
