On Fri, 2002-04-26 at 17:09, Camm Maguire wrote:
> Greetings, and thanks for your report! Are you using the Debian
> package? If not, what version of maxima, and what underlying lisp?
>
> If you are using the Debian package, I'd be most appreciative if you
> would submit a bug through the Debian Bug Tracking System. In any
> case, I'll forward this to the maxima list on your behalf.
>
> Take care,
>
> Cyril Guyot <cyril@zoy.org> writes:
>
> > Dear Camm,
> >
> > I think there is a bug in the primep routine of maxima. I believe
> > 340282366762482138434845932244680310783 is prime but it does not seem to
> > be recognized as such by maxima.
Wow. I admire your patience. How long did it take
primep(340282366762482138434845932244680310783)
to finish? I lost patience after 30 minutes or so.
> I don't think so since on my machine primep(80630964769); returns
FALSE
> and primep(80630965313); returns TRUE both in less than a second.
> However they are both prime. Also the first one seems to return nearly
> instantaneously whereas the second takes around a second to return a
> positive answer. It seems some early abort strategy should not be
> triggered there.
>
> Just to add some information, I am using the maxima package from the
> debian unstable which seems to use gcl version 2.4.0 as the underlying
> lisp.
That is crucial information. Maxima returns TRUE for both
primep(80630964769)
primep(80630965313)
I use Clisp or CMUCL. It looks like a GCL bug, but it will require a
little more investigation.
Thanks for the report.
--Jim