#12970: MPIR fails to build when CPU's architecture name doesn't match its
actual
capabilities
-----------------------------------------------+----------------------------
Reporter: kini | Owner: tbd
Type: defect | Status: new
Priority: major | Milestone: sage-5.1
Component: packages | Resolution:
Keywords: mpir virtualbox yasm cflags | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Jeroen Demeyer | Merged in:
Dependencies: | Stopgaps:
-----------------------------------------------+----------------------------
Changes (by {'newvalue': u'Jeroen Demeyer', 'oldvalue': ''}):
* author: => Jeroen Demeyer
Old description:
> Specifically, on a Virtualbox virtual machine running on a Intel i5-2500K
> CPU, which is of the architecture GCC calls "corei7-avx", the virtual CPU
> visible to programs running inside the virtual machine does not actually
> support all the instructions that a real physical i5-2500K CPU does.
>
> The MPIR SPKG currently builds its own yasm with CFLAGS containing
> `-march=corei7-avx` (after detecting the name of the CPU architecture in
> the VM). The resulting yasm apparently produces instructions that are not
> understood by the virtual CPU. If one builds yasm with CFLAGS containing
> `-march=native` instead, the problem does not occur. So a solution seems
> to be to force MPIR to build its yasm with `-march=native`, but I don't
> know how that will impact platforms other than my Virtualbox VM.
New description:
Specifically, on a Virtualbox virtual machine running on a Intel i5-2500K
CPU, which is of the architecture GCC calls "corei7-avx", the virtual CPU
visible to programs running inside the virtual machine does not actually
support all the instructions that a real physical i5-2500K CPU does.
The MPIR SPKG currently builds its own yasm with CFLAGS containing
`-march=corei7-avx` (after detecting the name of the CPU architecture in
the VM). The resulting yasm apparently produces instructions that are not
understood by the virtual CPU. If one builds yasm with CFLAGS containing
`-march=native` instead, the problem does not occur. So a solution seems
to be to force MPIR to build its yasm with `-march=native`, but I don't
know how that will impact platforms other than my Virtualbox VM.
'''untested spkg''':
[http://boxen.math.washington.edu/home/jdemeyer/spkg/mpir-2.4.0.p5.spkg]
--
Comment:
Please test the spkg
[http://boxen.math.washington.edu/home/jdemeyer/spkg/mpir-2.4.0.p5.spkg]
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12970#comment:9>
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.
