#13137: upgrade MPIR to 2.6.0
-------------------------------------------------------------------------+--
Reporter: jhpalmieri |
Owner: tbd
Type: enhancement |
Status: needs_review
Priority: major |
Milestone: sage-5.6
Component: packages |
Resolution:
Keywords: mpir spkg |
Work issues:
Report Upstream: N/A |
Reviewers: Jeroen Demeyer
Authors: John Palmieri, Jean-Pierre Flori, Karl-Dieter Crisman |
Merged in:
Dependencies: #13755 |
Stopgaps:
-------------------------------------------------------------------------+--
Comment (by jpflori):
Replying to [comment:92 leif]:
> Replying to [comment:91 jpflori]:
> > Ok it failed with older MPIR as well, please have a look at build logs
here:
> > https://groups.google.com/d/topic/sage-release/ngw_EiBaY0Q/discussion
>
> Well, that's a single failure, [although] in `nuss_mul()`[too] (and on
an Apple ''of course^TM^'')... ;-)
>
Hmmm, the reports on sage-release for 5.6.beta3 also point that there is a
problem with zn_poly on top of MPIR 2.4.x [on OS X], and I don't know why
but I have strong suspicion it could be in nuss_mul [as well].
> One would probably have to run ''the tuning'' multiple times under heavy
load to reproduce this; haven't at all looked at the code...
The problem is not during the tuning phase but during the quick test one.
The testing code is quite simple, it multiplies two (large) polys using
FFT:
* first with the zn_poly code,
* then with the underlying MPIR/GMP code (using KS)
and compare the results.
So a potential culprit was the new MPIR FFT, but as the [same] bug seemed
to happen with older version of MPIR and the FFT code was completely
changed inbeetween, we can mostly rule out that MPIR is to blame.
It looks like we have to blame zn_poly, which is unfortunate because it is
unmaintained.
And remember I mentioned I get segfaults quite often in different places
as well on Cygwin when building zn_poly during the tuning phase (and
tuning the threshold for FFT IIRC).
So it does not seem completely crazy to blame zn_poly rather than MPIR for
the other problem as well.
Of course a good test would be to try to reproduce the error on the
problematic systems but on top of GMP.
If the problem persists, I guess we can definitely rule out that MPIR is
buggy.
>
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13137#comment:93>
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.
