https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100444
--- Comment #12 from Edward Cree ---
A datum: booting with 'nordrand' on the kernel command line does not affect
this, the test program still prints 4294967295. (Yet '/proc/cpuinfo' no longer
mentions rdrand or rdseed in flags. Stdlib must be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100444
--- Comment #7 from Edward Cree ---
(In reply to Richard Biener from comment #4)
> people that
> cannot be bothered to update their ucode or the kernel are not likely
> bothered to update libstdc++ either.
Fwiw, my kernel is fairly up-to-date
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100444
--- Comment #2 from Edward Cree ---
(In reply to Richard Biener from comment #1)
> Isn't this worked around at kernel level by disabling RDRAND support on
> affected CPUs?
Not sure. I wondered if it might be, so I straced the process and it
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:
