From: "Koning, Paul" <Paul.Koning@dell.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Alexandre Oliva <oliva@adacore.com>,
"libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: require et random_device for cons token test
Date: Wed, 24 Mar 2021 13:22:17 +0000 [thread overview]
Message-ID: <C7C49A9E-7A56-438E-8740-065DBF29C2FF@dell.com> (raw)
In-Reply-To: <20210324085907.GD3008@redhat.com>
> On Mar 24, 2021, at 4:59 AM, Jonathan Wakely via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>
> On 24/03/21 03:53 -0300, Alexandre Oliva wrote:
>>
>> On target systems that don't support any random_device, not even the
>> default one,
>
> It should be impossible to have no random_device.
Not true; deeply embedded systems might not have one. Among GCC platforms, pdp11 doesn't have one, and at least some vax platforms probably don't either.
> As a fallback a
> pseudo random number generator should be used.
Presumably yes -- it seems unlikely that GCC tests depend on cryptographic strength of the random nummber generator. If a PRNG is used then the classic FORTRAN "random" function would serve.
paul
next prev parent reply other threads:[~2021-03-24 13:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 6:53 Alexandre Oliva
2021-03-24 8:59 ` Jonathan Wakely
2021-03-24 10:33 ` Alexandre Oliva
2021-03-24 11:27 ` Jonathan Wakely
2021-03-24 14:01 ` Jonathan Wakely
2021-03-25 10:17 ` Alexandre Oliva
2021-03-25 11:57 ` Jonathan Wakely
2021-03-26 19:17 ` Jonathan Wakely
2021-03-25 11:03 ` Alexandre Oliva
2021-03-25 11:39 ` Jonathan Wakely
2021-03-25 11:00 ` Alexandre Oliva
2021-03-25 11:38 ` Jonathan Wakely
2021-11-09 15:02 ` Jonathan Wakely
2021-03-24 10:55 ` Jonathan Wakely
2021-03-24 13:22 ` Koning, Paul [this message]
2021-03-24 13:38 ` Jonathan Wakely
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=C7C49A9E-7A56-438E-8740-065DBF29C2FF@dell.com \
--to=paul.koning@dell.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=oliva@adacore.com \
/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).