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++/97311] Bug in std::seed_seq::generate() when integer type has more than 32 bits Date: Wed, 07 Oct 2020 20:55:43 +0000 [thread overview] Message-ID: <bug-97311-4-P4ARkYvoLb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97311-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97311 --- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> --- I can't get the algorithm to ever produce an intermediate result that doesn't fit in 32 bits, so I'm not sure there's actually a problem here in practice.
next prev parent reply other threads:[~2020-10-07 20:55 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-07 5:57 [Bug libstdc++/97311] New: " kristian.spangsege at gmail dot com 2020-10-07 13:10 ` [Bug libstdc++/97311] " redi at gcc dot gnu.org 2020-10-07 13:31 ` redi at gcc dot gnu.org 2020-10-07 18:58 ` kristian.spangsege at gmail dot com 2020-10-07 20:23 ` redi at gcc dot gnu.org 2020-10-07 20:28 ` redi at gcc dot gnu.org 2020-10-07 20:55 ` redi at gcc dot gnu.org [this message] 2020-10-07 21:12 ` redi at gcc dot gnu.org 2020-10-09 16:05 ` cvs-commit at gcc dot gnu.org 2020-10-09 16:06 ` 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-97311-4-P4ARkYvoLb@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).