Le 10/08/2013 19:06, Julien Puydt a écrit :
testing experimental sage builds, I noticed the following very peculiar
result:
sage: pari(2^100-1)
297747071055821155548899525576506736639
sage: 2^100-1
1267650600228229401496703205375
age: pari(2)^100-1
1267650600228229401496703205375
Does
Le 10/08/2013 22:16, Volker Braun a écrit :
Since the factorization starts with 2^64 it looks like there is
something wrong with how uint64_t is being used in the computation.
Possibly a 32-bit/64-bit problem.
The following computation is even more interesting:
sage: n=2^100-1;n
Whats experimental about it? unstable pari, compiler, both? The currently
stable Pari has at least one bug
with unspecified behavior in a setjmp() that may be cause trouble depending
on the compiler.
On Monday, August 12, 2013 11:19:29 AM UTC+1, Snark wrote:
Le 10/08/2013 22:16, Volker
Le 12/08/2013 13:20, Volker Braun a écrit :
Whats experimental about it? unstable pari, compiler, both? The
currently stable Pari has at least one bug
with unspecified behavior in a setjmp() that may be cause trouble
depending on the compiler.
It's experimental because it's Felix Salfelder's
Le 12/08/2013 12:19, Julien Puydt a écrit :
Le 10/08/2013 22:16, Volker Braun a écrit :
Since the factorization starts with 2^64 it looks like there is
something wrong with how uint64_t is being used in the computation.
Possibly a 32-bit/64-bit problem.
The following computation is even
On Monday, August 12, 2013 12:36:45 PM UTC+1, Snark wrote:
It's experimental because it's Felix Salfelder's build system.
So I guess that means Pari without patches/mp.c.patch
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from
Le 12/08/2013 13:46, Volker Braun a écrit :
On Monday, August 12, 2013 12:36:45 PM UTC+1, Snark wrote:
It's experimental because it's Felix Salfelder's build system.
So I guess that means Pari without patches/mp.c.patch
The patch was applied, I see it in the logs.
Snark
--
You
Le 12/08/2013 13:46, Volker Braun a écrit :
On Monday, August 12, 2013 12:36:45 PM UTC+1, Snark wrote:
It's experimental because it's Felix Salfelder's build system.
So I guess that means Pari without patches/mp.c.patch
The pari as built by Felix' system has the patch applied ; since
Hi,
testing experimental sage builds, I noticed the following very peculiar
result:
sage: pari(2^100-1)
297747071055821155548899525576506736639
sage: 2^100-1
1267650600228229401496703205375
age: pari(2)^100-1
1267650600228229401496703205375
Does someone know what can produce this kind of...
It does not happen to me on sage-5.11.rc0:
++
| Sage Version 5.11.rc0, Release Date: 2013-07-31|
| Type notebook() for the browser-based notebook interface.|
| Type help() for help.
Le 10/08/2013 19:18, John Cremona a écrit :
It does not happen to me on sage-5.11.rc0:
Oh, 5.11.rc releases have started?
In any case, I know no sage release has the issue ; as I said, that was
with *experimental* sage builds. What I'm trying to understand is how
it's even possible to get
for what it's worth, here's some info on that first response...
factor(297747071055821155548899525576506736639 +1);
= 2^64*3*5*1064269*1011079032619
--
You received this message because you are subscribed to the Google Groups
sage-devel group.
To unsubscribe from this group and stop receiving
Le 10/08/2013 21:04, rjf a écrit :
for what it's worth, here's some info on that first response...
factor(297747071055821155548899525576506736639 +1);
= 2^64*3*5*1064269*1011079032619
Sorry, but I fail to see the relevance of this with what I see...
Snark on #sagemath
--
You received this
Since the factorization starts with 2^64 it looks like there is something
wrong with how uint64_t is being used in the computation. Possibly a
32-bit/64-bit problem.
On Saturday, August 10, 2013 8:30:06 PM UTC+1, Snark wrote:
Le 10/08/2013 21:04, rjf a �crit :
for what it's worth, here's
14 matches
Mail list logo
