It is worth checking that this specific prime still passes the test with reentrant switched on and that the error is not just going away because of different random seeds or something. Perhaps try inserting this number explicitly into the test code to check it is not declared composite. It is in fact prime.
Bill. 2010/1/5 Cactus <rieman...@googlemail.com>: > > > On Jan 5, 10:16 am, Cactus <rieman...@googlemail.com> wrote: >> I am seeing an error reported on the mpz_likely_prime test: >> >> mpz_likely_prime_p >> 18158515892286259199 is declared composite >> >> I know we had issues in the past but I thought that they had been >> sorted. >> >> Is this not so? > > I have found that this bug is triggered on Windows by using > WANT_TMP_ALLOCA. If I go back to using WANT_TMP_REENTRANT all is > well. > > Which is a pity since it would have been nice to align the Windows > build with the Linux/GCC one. > > Brian > > > > >> Brian > > -- > > You received this message because you are subscribed to the Google Groups > "mpir-devel" group. > To post to this group, send email to mpir-de...@googlegroups.com. > To unsubscribe from this group, send email to > mpir-devel+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/mpir-devel?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to mpir-de...@googlegroups.com. To unsubscribe from this group, send email to mpir-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.