https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113430
--- Comment #11 from Dimitrij Mijoski ---
(In reply to Sam James from comment #10)
> I don't plan on pursuing it myself, leaving it to someone else, as I can't
> reproduce on my main workstation and I don't want to faff w/ kernel config.
You
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113430
Dimitrij Mijoski changed:
What|Removed |Added
CC||dmjpp at hotmail dot com
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 #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 #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 #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 #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
>
: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: dmjpp at hotmail dot com
Target Milestone: ---
Text in valid Unicode should never contain surrogate code POINTS. Those are
only allowed in UTF-16, but only as code UNITS and must be properly paired.
UTF-8 text
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106656
Dimitrij Mijoski changed:
What|Removed |Added
CC||dmjpp at hotmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98466
--- Comment #3 from Dimitrij Mijoski ---
(In reply to Jonathan Wakely from comment #2)
> This was already fixed on master by r11-6682
> 05a30af3f237984b4dcf1dbbc17fdac583c46506
Yes, that patch mostly fixes bug 70303, too. With that patch, the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98466
Dimitrij Mijoski changed:
What|Removed |Added
CC||dmjpp at hotmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86419
--- Comment #12 from Dimitrij Mijoski ---
Hello Jonathan. I posted a patch for this bug which I hope you'll find it
useful once you start working on this.
https://gcc.gnu.org/pipermail/libstdc++/2020-September/051073.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97076
Dimitrij Mijoski changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: dmjpp at hotmail dot com
Target Milestone: ---
This is not a bug in GCC, but in the supporting files in contrib. The
clang-format file at the end has Standard: Cpp03. See
https://gcc.gnu.org/git/?p=gcc.git;a=blob;f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86419
--- Comment #10 from Dimitrij Mijoski ---
I was wrong in comment #9. The bug and the proposed fix are ok in comment #7.
While writing some tests for error I discovered yet another bug in UTF-8
decoding. See the example:
// 2 code points, both
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86419
--- Comment #9 from Dimitrij Mijoski ---
Ignore my last comment, here is it fixed.
Looking again at my proposed fix in comment #7, i concluded it is not the best
fix. It will fix the testsuite in the same comment #7, but I discovered another
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86419
--- Comment #8 from Dimitrij Mijoski ---
Looking again at my proposed fix in comment #6, i concluded it is not the best
fix. It will fix the testsuite in the same comment #6, but I discovered another
class of errors related to the lines I am
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86419
--- Comment #7 from Dimitrij Mijoski ---
I think a found a related bug in the UTF8 to UCS2 codecvt,
codecvt_utf8. It can be tested with the following example:
#include
auto test_u8_ucs2_in()
{
// 2 code points, one is 3 bytes and the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86419
--- Comment #5 from Dimitrij Mijoski ---
I think I found where the bug lies. It lies in
1. line 557 of the file c++11/codecvt.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86419
Dimitrij Mijoski changed:
What|Removed |Added
Summary|codecvt::in() and out()|...>::in() and out()
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85494
--- Comment #6 from Dimitrij Mijoski ---
I read the patch couple of times and seems completely OK. Can you push it to
the repository (or to a fork)?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86419
Dimitrij Mijoski changed:
What|Removed |Added
Attachment #44359|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86419
--- Comment #1 from Dimitrij Mijoski ---
Created attachment 44359
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44359=edit
test cases that trigger the bug
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: dmjpp at hotmail dot com
Target Milestone: ---
I have created a bunch of test cases, and on some it fails unexpectedly. I'll
post the code as attachment, the lines with the bug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85494
--- Comment #3 from Dimitrij Mijoski ---
Created attachment 44358
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44358=edit
implements proper random_device for mingw-w64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85494
Dimitrij Mijoski changed:
What|Removed |Added
CC||dmjpp at hotmail dot com
--- Comment
27 matches
Mail list logo
