https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100444
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Richard Biener from comment #4) > Thus I believe the issue is mitigated at the kernel level and people that Yes, that's my understanding. > cannot be bothered to update their ucode or the kernel are not likely > bothered to update libstdc++ either. Note handling it above would > raise a runtime error rather than falling back to other sources of > randomness. > Doing the checking where we detect rdrand support would avoid that. I suppose we could use the rdrand instruction a couple of times when doing the cpuid support, and if it gives the same value conclude it's broken and so not available. But as you say, people who haven't bothered to update microcode probably aren't going to get a libstdc++ update either.
