#8664: Upgrade Sage's MPIR spkg to version 2.1.3
-------------------------------------------------------------------------------+
Reporter: was
| Owner: GeorgSWeber
Type: enhancement
| Status: needs_work
Priority: major
| Milestone: sage-4.7
Component: packages
| Resolution:
Keywords: GMP ECM execstack Fedora 14 extension module library dependencies
| Author: Mike Hansen, Leif Leonhardy
Upstream: N/A
| Reviewer: Leif Leonhardy, Dmitrii Pasechnik
Merged:
| Work_issues: Use MPIR's optimized CFLAGS
-------------------------------------------------------------------------------+
Comment(by leif):
Replying to [comment:102 jdemeyer]:
> Replying to [comment:100 leif]:
> > The `CFLAGS` (or `-march=`) issue is IMHO completely unrelated -- if
not irrelevant. ;-)
>
> The current MPIR spkg ''does'' use machine-specific CFLAGS, the new spkg
on this ticket ''does not''. This is a step backwards.
>
> If you think it is irrelevant, please explain why...
Give me a ''realistic'' showcase where that matters... (i.e., causes a
significant decrease in performance) ;-)
First of all, the important parts of MPIR are (more or less) hand-
optimized assembly code, selected by MPIR's `configure` (or its
parameters*) to best match the detected architecture (where MPIR's
`config.guess` doesn't always necessarily choose the current nearest one
btw.).
A properly configured GCC is usually sufficient, i.e. should default to
something like `-march=native` (or a small subset of processors the actual
CPU fits into), at least for people to whom performance is really crucial.
With my ''current'' spkg here, the user can always (intentionally or not)
use the "global" `CFLAGS`, i.e. specify whatever is most appropriate to
him or her.
The spkg had been extensively tested -- as is, month ago. As always: New
changes, new pitfalls. [And even more delay due to a new test / review
cycle. That's why I did not make any further changes ''on this ticket''.
Speaking of the devil, can someone '''please''' give #5847 a positive
review?]
----
* If I haven't already, one (or me) should implement `MPIR_EXTRA_OPTS` or
whatever it was called (but I think I already did).
P.S.: Ah, I see. It's already in the p1 here.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8664#comment:103>
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.
