[Gmp-commit] /var/hg/www: Reinstate seeding entry, with updates.

mercurial at gmplib.org mercurial at gmplib.org
Fri Nov 18 00:36:41 UTC 2016


details:   /var/hg/www/rev/563fec0cc726
changeset: 235:563fec0cc726
user:      Torbjorn Granlund <tg at gmplib.org>
date:      Fri Nov 18 01:36:33 2016 +0100
description:
Reinstate seeding entry, with updates.

diffstat:

 devel/mini-gmp-status.html |  12 +++++-------
 1 files changed, 5 insertions(+), 7 deletions(-)

diffs (36 lines):

diff -r 7cd0c37f9ba8 -r 563fec0cc726 devel/mini-gmp-status.html
--- a/devel/mini-gmp-status.html	Thu Nov 17 23:02:34 2016 +0100
+++ b/devel/mini-gmp-status.html	Fri Nov 18 01:36:33 2016 +0100
@@ -30,7 +30,7 @@
       </td>
       <td style="text-align:center;">
 	<span style="font-size:200%;">Mini-GMP status</span> <br>
-	<span style="font-size:75%;">Last modified: 2016-11-16 </span>
+	<span style="font-size:75%;">Last modified: 2016-11-18 </span>
       </td>
     </tr>
   </table>
@@ -78,7 +78,7 @@
 
 <li style="background-color:#806030;">
   The mini-gmp check target fails when the main build does not use the compiler
-  default ABI.  This affects hundreds of config.
+  default ABI.  This affects hundreds of configs.
 
 <li style="background-color:#806030;">
   <del>
@@ -133,11 +133,9 @@
   <del>According to valgrind, t-str leaks many MiB of memory in tens of thousands blocks.</del>
 
 <li style="background-color:#306030;">
-  <del>
-  The seeding triggered by GMP_CHECK_RANDOMIZE is apparently based on seconds
-  since epoch (with some funny skew).  This is not good enough, as tests which
-  run at the same time will get the same seed.
-  </del>
+  The seeding triggered by GMP_CHECK_RANDOMIZE is based on seconds since epoch
+  plus getpid().  This is not good enough, there will in practice be many
+  collisions over the test machine park.  Fix: Copy GMP's seeding code.
 
 <li style="background-color:#803030;">
   Arithmetic problems triggered by t-powm, demonstrated by


More information about the gmp-commit mailing list