public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/105081] Make std::random_device throw std::system_error Date: Fri, 30 Jun 2023 14:09:24 +0000 [thread overview] Message-ID: <bug-105081-4-yeJMRG42dj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105081-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105081 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:d6a6a4ea086d6af97bd7fbd482f51df41c265b79 commit r14-2217-gd6a6a4ea086d6af97bd7fbd482f51df41c265b79 Author: Jonathan Wakely <jwakely@redhat.com> Date: Fri Jun 30 14:37:59 2023 +0100 libstdc++: Make std::random_device throw more std::system_error [PR105081] In r14-289-gf9412cedd6c0e7 I made the std::random_device constructor throw std::system_error for unrecognized tokens. But it still throws std::runtime_error for a token such as "rdseed" that is recognized but not supported at runtime by the CPU the program is running on. With this change we throw std::system_error for those cases too. This fixes the following failures on Intel CPUs withour rdseed support: FAIL: 26_numerics/random/random_device/94087.cc execution test FAIL: 26_numerics/random/random_device/cons/token.cc execution test FAIL: 26_numerics/random/random_device/entropy.cc execution test libstdc++-v3/ChangeLog: PR libstdc++/105081 * src/c++11/random.cc (random_device::_M_init): Throw std::system_error when the requested device is a valid token but not available at runtime.
prev parent reply other threads:[~2023-06-30 14:09 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-28 11:38 [Bug libstdc++/105081] New: " redi at gcc dot gnu.org 2022-03-28 11:38 ` [Bug libstdc++/105081] " redi at gcc dot gnu.org 2023-01-18 13:31 ` redi at gcc dot gnu.org 2023-04-26 6:55 ` rguenth at gcc dot gnu.org 2023-04-27 10:29 ` cvs-commit at gcc dot gnu.org 2023-04-27 10:36 ` redi at gcc dot gnu.org 2023-06-30 14:09 ` cvs-commit at gcc dot gnu.org [this message]
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-105081-4-yeJMRG42dj@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).