[Bug c++/115524] New: Cygwin: Space character categorized as non-printable by std::ctype

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115524 Bug ID: 115524 Summary: Cygwin: Space character categorized as non-printable by std::ctype Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal

[Bug libstdc++/37475] codecvt::do_in/do_out functions return "ok" when the output sequence has zero length

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37475 --- Comment #14 from Kristian Spangsege --- Is the underscore intended before `Guard` in `explicit _Guard(__c_locale) { }` for the GLIBC <= 2.2 case? Besides that, the full patch looks correct to me.

[Bug libstdc++/37475] codecvt::do_in/do_out functions return "ok" when the output sequence has zero length

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37475 --- Comment #12 from Kristian Spangsege --- These changes look good to me. A couple of points: * Should the `else`s still be there now that the preceding branches terminate with `break`? * `do_out()` has the same problem as `do_in()`. * If

[Bug libstdc++/37475] [DR 382] codecvt::do_in/do_out functions return "ok" when the output sequence has zero length

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37475 --- Comment #7 from Kristian Spangsege --- This bug still exists in GCC 14.0.1. This was tested with the attacked test_2.cpp. The actual result is `ok`, but it should have been `partial`. Curiously, this bug does not occur when using the Cygwin

[Bug libstdc++/37475] [DR 382] codecvt::do_in/do_out functions return "ok" when the output sequence has zero length

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37475 --- Comment #6 from Kristian Spangsege --- Created attachment 58405 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58405=edit Test whether bug still exists in GCC 14.0.1

[Bug c++/113063] Strange linker error in special case involving local class with defaulted spaceship operator and static assert

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113063 --- Comment #6 from Kristian Spangsege --- Thanks for fixing it. Should it be back-ported to earlier GCC versions? From my point of view, as far back as GCC 11 would be nice.

[Bug c++/113063] Strange linker error in special case involving local class with defaulted spaceship operator and static assert

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113063 --- Comment #1 from Kristian Spangsege --- By the way, and as expected, this problem does not exist in Clang.

[Bug c++/113063] New: Strange linker error in special case involving local class with defaulted spaceship operator and static assert

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113063 Bug ID: 113063 Summary: Strange linker error in special case involving local class with defaulted spaceship operator and static assert Product: gcc Version:

[Bug libstdc++/37475] [DR 382] codecvt::do_in/do_out functions return "ok" when the output sequence has zero length

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37475 Kristian Spangsege changed: What|Removed |Added CC||kristian.spangsege at gmail dot co

[Bug libstdc++/97311] Bug in std::seed_seq::generate() when integer type has more than 32 bits

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97311 --- Comment #3 from Kristian Spangsege --- I would recommend not locking arithmetic to std::uint32_t, and instead working with std::uint_fast32_t, because I can imaging a platform (current or future) where 32-bit arithmetic is slower that 64-bit

[Bug libstdc++/97311] New: Bug in std::seed_seq::generate() when integer type has more than 32 bits

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97311 Bug ID: 97311 Summary: Bug in std::seed_seq::generate() when integer type has more than 32 bits Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal