#11616: Upgrade MPIR to a more recent upstream release
---------------------------+------------------------------------------------
Reporter: leif | Owner: leif
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-4.7.2
Component: packages | Keywords: GMP, SandyBridge, Westmere
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies: #8664 #5847
---------------------------+------------------------------------------------
Changes (by leif):
* status: new => needs_review
Old description:
> This is a follow-up to #8664.
>
> The following spkgs are based on the '''not yet positively reviewed'''
> MPIR 2.1.3.p4 spkg from #8664:
>
> * http://spkg-upload.googlecode.com/files/mpir-2.3.1.p0.spkg [[BR]]
> md5sum: `ff0104e302611e49604a1c4ead97cbf4 mpir-2.3.1.p0.spkg`
>
> * http://spkg-upload.googlecode.com/files/mpir-2.4.0.p0.spkg [[BR]]
> md5sum: `98e04aa43ceef04d83574f0ee8e152fc mpir-2.4.0.p0.spkg`
>
> You may want to give them a try ''now'' though. (The former is just
> intended as a "fallback" spkg in case problems introduced in the latter
> should arise.)
>
> The list of changes between MPIR 2.1.3 (more precisely, 2.1.1) and MPIR
> 2.4.0 is fairly long, so I haven't put them into the description. I'll
> perhaps attach them as a text file later.
>
> For instructions on how to install / test the spkgs please see #8664, as
> these two also require the new GMP-ECM 6.3.p2 spkg from #5847 and two
> patches to the Sage library (one from each ticket); a Sage 4.7.1.rc0
> (Sage library) spkg with these two patches already applied
> [comment:ticket:8664:114 is also available] ''there''.
>
> ----
>
> === mpir-2.4.0.p0 (Leif Leonhardy, July 21st, 2011) ===
> * Upstream upgrade to MPIR 2.4.0 (#11616).
>
> === mpir-2.3.1.p0 (Leif Leonhardy, July 20th, 2011) ===
> * Upstream upgrade to MPIR 2.3.1 (#11616).
> * Clean up .hgtags.
>
> === mpir-2.1.3.p4 (Leif Leonhardy, July 19th, 2011) ===
> * #8664: Upgrade Sage's MPIR spkg to version 2.1.3 [[BR]]
> ...
New description:
This is a follow-up to #8664.
The following spkgs are based on the (not yet merged) MPIR 2.1.3.p4 spkg
from #8664:
* http://spkg-upload.googlecode.com/files/mpir-2.3.1.p0.spkg [[BR]]
md5sum: `ff0104e302611e49604a1c4ead97cbf4 mpir-2.3.1.p0.spkg`
* http://spkg-upload.googlecode.com/files/mpir-2.4.0.p0.spkg [[BR]]
md5sum: `98e04aa43ceef04d83574f0ee8e152fc mpir-2.4.0.p0.spkg`
You may want to give them a try ''now'' though. (The former is just
intended as a "fallback" spkg in case problems introduced in the latter
should arise.)
The list of changes between MPIR 2.1.3 (more precisely, 2.1.1) and MPIR
2.4.0 is fairly long, so I haven't put them into the description, but
[attachment:MPIR_upstream_changes_between_2.1.1_and_2.4.0.txt attached
them] in a plain text file.
For instructions on how to install / test the spkgs please see #8664, as
these two also require the new GMP-ECM 6.3.p2 spkg from #5847 and two
patches to the Sage library (one from each ticket); a Sage 4.7.1.rc0 (Sage
library) spkg with these two patches already applied
[comment:ticket:8664:114 is also available] ''there''.
Note that #5847 technically again '''needs review''' because I had to
rebase the trivial one-line patch attached there.
----
=== mpir-2.4.0.p0 (Leif Leonhardy, July 21st, 2011) ===
* Upstream upgrade to MPIR 2.4.0 (#11616).
=== mpir-2.3.1.p0 (Leif Leonhardy, July 20th, 2011) ===
* Upstream upgrade to MPIR 2.3.1 (#11616).
* Clean up .hgtags.
=== mpir-2.1.3.p4 (Leif Leonhardy, July 19th, 2011) ===
* #8664: Upgrade Sage's MPIR spkg to version 2.1.3 [[BR]]
...
--
Comment:
Setting this to "needs review" since the MPIR 2.1.3.p4 from #8664 got
positive review again, though so far only by a single reviewer.
The current packages are mainly meant for '''testing the new upstream
releases''', hopefully on a variety of platforms supported by Sage; some
improvements or changes to Sage's part will most probably follow.
It would just be nice to ''relatively early'' know whether any of them
(more important, MPIR 2.4.0) causes any problems on one of our platforms.
(MPIR 2.5.0 is scheduled for September 1st, which isn't that far...)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11616#comment:2>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" 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/sage-trac?hl=en.
