Marc -
Thanks for your response. After some investigation, it appears that
the only changes needed are in autoconf, so I don't think anything
needs to be done to libgmp for the moment.
Once things have stabilized, we may be able to see about how to get a
computer in the compile farm. For now,
"Marco Bodrato" writes:
Il Lun, 14 Novembre 2016 3:49 pm, Torbjörn Granlund ha scritto:
> 2. There are inexplicable timeouts (or possibly excessive memory use)
>triggered by t-pprime_p for some of our systems:
>Perhaps the test is simply too slow, or
t...@gmplib.org (Torbjörn Granlund) writes:
> I created a web page for tracking the mini-gmp problems:
>
> https://gmplib.org/devel/mini-gmp-status.html
From that page:
(P2) The seeding triggered by GMP_CHECK_RANDOMIZE is apparently based on
seconds since epoch (with some funny skew).
I created a web page for tracking the mini-gmp problems:
https://gmplib.org/devel/mini-gmp-status.html
I'd like to stress that mini-gmp problems do not affect the quality of
GMP itself. GMP uses mini-gmp for some bootstrapping tasks, but that's
known to work properly for both 32-bit and
Ciao,
Il Lun, 14 Novembre 2016 3:49 pm, Torbjörn Granlund ha scritto:
> 2. There are inexplicable timeouts (or possibly excessive memory use)
>triggered by t-pprime_p for some of our systems:
>Perhaps the test is simply too slow, or its time varies hugely, or it
>hits an infinite
I recently enabled automated testing of mini-gmp, the little
library-in-the-library which comes with GMP. It has thus far discovered
these problems:
1. GMP_CHECK_RANDOMIZE is not always printed for failing tests. This
makes it hard to reproduce intermittent failures. It needs to be