Bill Allombert on Fri, 16 May 2014 12:04:38 +0200

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

pari-2.7.1(STABLE) released

Dear PARI lovers,

I would like to announce the release of pari-2.7.1 (STABLE). The sources
and a basic Windows binary are available from

This is a BUGFIX release for the stable branch. 
This release addresses in particular a problem with 'make install' on OS X,
some integer overflows on 32bit systems, and all significant problems that
could be fixed in a simple, harmless way. However we strongly encourage you to
upgrade since it fixes a number of cases where PARI was returning an incorrect

  --- For Windows users: ---

An installer package is available at:

  --- For Android users: ---

  An updated PariDroid package will be available soon.


Thanks to all those who reported problems, on the mailing lists or through
our Bug Tracking System. ( See ), or
who tested the preleases.

Have fun,

  Bill and Karim

P.S: The Changelog:

Done for version 2.7.1 (released 16/05/2014):
[last column crossreferences current development release 2.8.0]

    1- make install fails on OS/X: ln -s libpari.dylib libpari.dylib fails [F1]
    2- Q_pvalrem(t_FRAC) => wrong result                                   [F2]
    3- [] == 0 but []~ != 0  (now []~ == 0 as well) [#1560]                [F3]
BA  4- test-kernel did not work when using --mt=pthread                    [F4]
BA  5- ellheegner was using too much memory in some case                   [F5]
BA  6- ellap can overflow on 32-bit machine [#1558] (minimal fix)          [F6]
    7- nfhilbert(K,x,y, P above 2) could give wrong results [#1561]        [F7]
    8- gcd(1/2, 1+I*1.) -> SEGV [#1563]                                   [F10]
    9- mathnf(t_VEC) could corrupt input (change sign)                    [F11]
   10- [libpari] RgM_transmul did not work                                [F12]
   11- [libpari] Fq_issquare didn't support T=NULL                        [F13]
   12- [libpari] nfpow_u didn't handle non-integral rational numbers      [F14]
   13- eint1(0) -> stack overflow [#1568]                                 [F15]
   14- nfroots(, t_POL with leading coeff -1) could miss solutions        [F19]
   15- precprime(1) -> invalid t_INT [#1576]                              [F20]