https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108976
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108976
--- Comment #14 from GCC Commits ---
The releases/gcc-13 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:bd5e672303f5f777e8927a746d3ee42db21d871b
commit r13-8788-gbd5e672303f5f777e8927a746d3ee42db21d871b
Author: Dimitrij
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108976
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|13.3|13.4
--- Comment #13 from Jakub
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108976
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|--- |13.3
--- Comment #12 from Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108976
--- Comment #11 from Dimitrij Mijoski ---
(In reply to Jonathan Wakely from comment #10)
> I think it would be good to backport it, what do you think?
I don't really have strong need. Maybe porting only to v13 as that is pretty
straightforward
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108976
--- Comment #10 from Jonathan Wakely ---
I think it would be good to backport it, what do you think?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108976
--- Comment #9 from Dimitrij Mijoski ---
I believe this bug report should closed as resolved. Are there maybe plans for
back-porting?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108976
--- Comment #8 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:a8b9c32da787ea0bfbfc9118ac816fa7be4b1bc8
commit r14-4335-ga8b9c32da787ea0bfbfc9118ac816fa7be4b1bc8
Author: Dimitrij Mijoski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108976
--- Comment #7 from Dimitrij Mijoski ---
I put a second version of the patch
https://gcc.gnu.org/pipermail/libstdc++/2023-March/055667.html about a month
ago.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108976
--- Comment #6 from Dimitrij Mijoski ---
I sent a single patch to the mailing list with a good detailed commit message.
I think that is better than multiple patches.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108976
--- Comment #5 from Jonathan Wakely ---
Excellent, thanks! I'll look at the commits tomorrow and get back to you.
A patch will need to be submitted to the mailing lists, but it might be OK to
send a single diff for the whole series, but then I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108976
--- Comment #4 from Dimitrij Mijoski ---
I have fixed this, added large testsute and discovered another bug in
codecvt_utf16 when the input [from, from_end) contains odd number of bytes.
Error was returned instead of partial.
Here are the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108976
--- Comment #3 from Jonathan Wakely ---
I have some new code for handling UTF-8 for std::print, and using that code
your relaxed u8str gets converted to 12 U+FFFD code points when printed to a
terminal, which I think is correct.
#include
int
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108976
--- Comment #2 from Dimitrij Mijoski ---
(In reply to Dimitrij Mijoski from comment #0)
> Those that read from UCS-2 seem to me like they properly report the error.
> Reading from UTF-16 can not have this bug by definition. From what I
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108976
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
15 matches
Mail list logo
