unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: Paul Eggert <eggert@cs.ucla.edu>, Eli Zaretskii <eliz@gnu.org>,
	peder@klingenberg.no, 42095@debbugs.gnu.org
Subject: bug#42095: 28.0.50; Build fails on Windows/MinGW64
Date: Mon, 29 Jun 2020 00:20:24 +0200	[thread overview]
Message-ID: <1600123.Sx1r6Z4Kui@omega> (raw)
In-Reply-To: <878sg819n2.fsf@klingenberg.no>

> > do we have any tests in our test suite to test the getrandom
> > function?
>
> No. Contributions would be welcome, I assume. Testing randomness is nontrivial,
> though.

Maybe Emacs has no unit test for getrandom(), but gnulib has:

https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob;f=tests/test-getrandom.c;h=0e9fbb0c26b9f54087be4cf7371b0488dba59f4e;hb=HEAD

It does not really check randomness. It only verifies that different calls
produce different results.

If someone wants to provide such tests, I recall that Knuth's TAOCP II
contains the mathematical foundations of such analysis.

Bruno






      parent reply	other threads:[~2020-06-28 22:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-27 21:28 bug#42095: 28.0.50; Build fails on Windows/MinGW64 Peder O. Klingenberg
2020-06-28 15:48 ` Eli Zaretskii
2020-06-28 19:36   ` Eli Zaretskii
2020-06-28 20:35     ` Paul Eggert
2020-06-29  2:28       ` Eli Zaretskii
2020-06-29  6:56         ` Paul Eggert
2020-06-29 14:52           ` Eli Zaretskii
2020-06-29 16:56             ` Paul Eggert
2020-06-29 18:45               ` Eli Zaretskii
2020-06-28 20:34   ` Paul Eggert
     [not found]   ` <e51b4ec2-2763-8d48-9724-2e26fe405373@cs.ucla.edu>
2020-06-29 14:13     ` Eli Zaretskii
     [not found]     ` <83r1ty0xk3.fsf@gnu.org>
2020-06-29 16:59       ` Paul Eggert
2020-06-28 22:20 ` Bruno Haible [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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1600123.Sx1r6Z4Kui@omega \
    --to=bruno@clisp.org \
    --cc=42095@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=peder@klingenberg.no \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).