public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc(refs/users/aoliva/heads/testme)] [libstdc++] [testsuite] expect zero entropy matching implementation Date: Fri, 23 Jun 2023 20:12:26 +0000 (GMT) [thread overview] Message-ID: <20230623201226.58A183858023@sourceware.org> (raw) https://gcc.gnu.org/g:36a0ffc5acb8bb5ecb583f41095964d2b62f71f5 commit 36a0ffc5acb8bb5ecb583f41095964d2b62f71f5 Author: Alexandre Oliva <oliva@adacore.com> Date: Fri Jun 23 17:09:49 2023 -0300 [libstdc++] [testsuite] expect zero entropy matching implementation random_device::get_entropy() returns 0.0 when _GLIBCXX_USE_DEV_RANDOM is not defined, but the test expects otherwise. Adjust. for libstdc++-v3/ChangeLog * testsuite/26_numerics/random/random_device/entropy.cc: Expect get_entropy to return zero when _GLIBCXX_USE_DEV_RANDOM is not defined. Diff: --- .../testsuite/26_numerics/random/random_device/entropy.cc | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/libstdc++-v3/testsuite/26_numerics/random/random_device/entropy.cc b/libstdc++-v3/testsuite/26_numerics/random/random_device/entropy.cc index 9f529f5d814..3e6872c8a61 100644 --- a/libstdc++-v3/testsuite/26_numerics/random/random_device/entropy.cc +++ b/libstdc++-v3/testsuite/26_numerics/random/random_device/entropy.cc @@ -13,7 +13,13 @@ test01() VERIFY( std::random_device(token).entropy() == 0.0 ); using result_type = std::random_device::result_type; +#ifdef _GLIBCXX_USE_DEV_RANDOM const double max = std::numeric_limits<result_type>::digits; +#else + // random_device::entropy() always returns 0.0 when + // _GLIBCXX_USE_DEV_RANDOM is not defined. + const double max = 0.0; +#endif for (auto token : { "/dev/random", "/dev/urandom" }) if (__gnu_test::random_device_available(token)) @@ -30,7 +36,7 @@ test01() VERIFY( entropy == max ); } - for (auto token : { "getentropy", "arc4random" }) + for (auto token : { "getentropy", "arc4random" }) if (__gnu_test::random_device_available(token)) { const double entropy = std::random_device(token).entropy();
next reply other threads:[~2023-06-23 20:12 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-23 20:12 Alexandre Oliva [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-06-14 19:17 Alexandre Oliva
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=20230623201226.58A183858023@sourceware.org \ --to=aoliva@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@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).