public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ecree429 at virginmedia dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/100444] New: std::random_device isn't random on AMD
Date: Thu, 06 May 2021 07:45:25 +0000	[thread overview]
Message-ID: <bug-100444-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100444

            Bug ID: 100444
           Summary: std::random_device isn't random on AMD
           Product: gcc
           Version: 10.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ecree429 at virginmedia dot com
  Target Milestone: ---

On certain AMD processors (in my case Ryzen 5 3600, stepping 0, microcode
0x8701013), RDRAND instruction is broken and always returns all-1s.  Thus e.g.
    #include <iostream>
    #include <random>

    int main(void)
    {
      static std::random_device rd;
      std::cout << rd() << '\n';
    }
always prints 4294967295.

Other RNG implementations such as Qt's QRandomGenerator detect this brokenness
and work around it, falling back to an alternate source of entropy.  libstdc++
should ideally do the same, rather than silently failing to be random.

             reply	other threads:[~2021-05-06  7:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06  7:45 ecree429 at virginmedia dot com [this message]
2021-05-06  7:52 ` [Bug libstdc++/100444] " rguenth at gcc dot gnu.org
2021-05-06  8:48 ` ecree429 at virginmedia dot com
2021-05-06  8:49 ` pinskia at gcc dot gnu.org
2021-05-06  8:58 ` rguenth at gcc dot gnu.org
2021-05-06 10:05 ` redi at gcc dot gnu.org
2021-05-06 10:22 ` redi at gcc dot gnu.org
2021-05-06 10:51 ` ecree429 at virginmedia dot com
2021-05-06 11:25 ` redi at gcc dot gnu.org
2021-05-06 11:39 ` rguenth at gcc dot gnu.org
2021-05-06 11:41 ` redi at gcc dot gnu.org
2021-05-10 20:20 ` redi at gcc dot gnu.org
2021-05-13 18:46 ` ecree429 at virginmedia dot com
2021-05-14  9:23 ` redi at gcc dot gnu.org
2021-09-25 20:07 ` redi at gcc dot gnu.org
2021-10-04 12:20 ` 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-100444-4@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: link
Be 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).