public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/60441] Incorrect textual representation for std::mersenne_twister_engine Date: Tue, 23 May 2023 12:14:11 +0000 [thread overview] Message-ID: <bug-60441-4-acK9aAJp49@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60441-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60441 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed|2018-08-07 00:00:00 |2023-5-23 --- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> --- The fix is quite simple, but it breaks compatibility between releases: diff --git a/libstdc++-v3/include/bits/random.tcc b/libstdc++-v3/include/bits/random.tcc index 24a5987db0d..8f53d5c5f53 100644 --- a/libstdc++-v3/include/bits/random.tcc +++ b/libstdc++-v3/include/bits/random.tcc @@ -486,9 +486,10 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION __os.flags(__ios_base::dec | __ios_base::fixed | __ios_base::left); __os.fill(__space); - for (size_t __i = 0; __i < __n; ++__i) + for (size_t __i = __x._M_p; __i < __n; ++__i) + __os << __x._M_x[__i] << __space; + for (size_t __i = 0; __i < __x._M_p; ++__i) __os << __x._M_x[__i] << __space; - __os << __x._M_p; __os.flags(__flags); __os.fill(__fill); @@ -512,7 +513,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION for (size_t __i = 0; __i < __n; ++__i) __is >> __x._M_x[__i]; - __is >> __x._M_p; + __x._M_p = 0; __is.flags(__flags); return __is;
next prev parent reply other threads:[~2023-05-23 12:14 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-03-06 8:49 [Bug libstdc++/60441] New: " koherde at hotmail dot com 2023-05-23 12:14 ` redi at gcc dot gnu.org [this message] 2023-05-23 13:40 ` [Bug libstdc++/60441] " redi at gcc dot gnu.org 2023-05-30 11:21 ` redi at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-60441-4-acK9aAJp49@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).