[Bug libstdc++/59974] ostream crashes on large numbers under Windows

2023-06-09 Thread steve at sk2 dot org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59974 --- Comment #6 from Stephen Kitt --- The patches were written by Jeff Epler, not me, so I can't assign copyright or sign off.

[Bug libstdc++/59974] ostream crashes on large numbers under Windows

2023-06-09 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59974 Jonathan Wakely changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

[Bug libstdc++/59974] ostream crashes on large numbers under Windows

2023-06-08 Thread 10walls at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59974 jon_y <10walls at gmail dot com> changed: What|Removed |Added CC||10walls at gmail dot co

[Bug libstdc++/59974] ostream crashes on large numbers under Windows

2014-01-28 Thread steve at sk2 dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59974 --- Comment #3 from Stephen Kitt --- Thanks for the quick feedback. It's not actually MinGW-w64 which is broken but the Windows runtime library; MinGW-w64 provides its own C99-compliant implementation of vsnprintf.

[Bug libstdc++/59974] ostream crashes on large numbers under Windows

2014-01-28 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59974 --- Comment #2 from Andrew Pinski --- C99 says they return the number of characters that would have been written for the return value of snprintf. Now older versions of glibc (2.0.6) are broken the same way mingw is broken.

[Bug libstdc++/59974] ostream crashes on large numbers under Windows

2014-01-28 Thread steve at sk2 dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59974 --- Comment #1 from Stephen Kitt --- Created attachment 31973 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31973&action=edit Proposed patch