That's interesting. Perhaps I have some corruption in my svn checked out repo.
To generate these I was merely picking random integers with a random number of bits from 0 to 32 and then taking nextprime. I was then running another primality test which I wrote. It kept returning errors, "n is declared composite". Of course n actually was composite, so my primality routine was working and mpz_nextprime was not. Anyhow, I suspect I have corruption. I'll try to track down the source of the problem. Bill. 2009/12/4 Case Vanhorsen <[email protected]>: > On Tue, Dec 1, 2009 at 9:33 AM, Bill Hart <[email protected]> wrote: >> It is the code Jason wrote: >> >> mpz_nextprime -> mpz_next_likely_prime ->mpz_likely_prime (by JM). >> >> At one point I switched over to the other implementation, but Jason >> raised the trial factoring bound and the problems seemed to go away. >> So it is currently using his code. But on win32 it is problematic for >> me. For example it declares the following likely prime: >> >> 3270390, 3387761, 21785199, 3270396 >> >> All of these have very small factors. > > I tried to duplicate the failures on my computer but I couldn't. I > tried both a Win32 VS build and a MinGW build via GMPY. I just called > next_prime with all the numbers from 3270390 back to the previous two > primes and I was getting correct results. How were you generating > these failures? > > casevh >> >> Bill. >> >> 2009/12/1 Jeff Gilchrist <[email protected]>: >>> On Tue, Dec 1, 2009 at 12:07 PM, Bill Hart <[email protected]> >>> wrote: >>>> mpz_nextprime seems to report lots of composites as primes on 32 bit >>>> machines, including some even numbers! Is this the same issue as we >>>> had on 64 bit machines? >>> >>> Is that the old built-in function or the new one Jason developed? >>> >>> Jeff. >>> >>> -- >>> >>> You received this message because you are subscribed to the Google Groups >>> "mpir-devel" group. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]. >>> 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 [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> 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 [email protected]. > To unsubscribe from this group, send email to > [email protected]. > 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
