#19280: MPIR gives incorrect result on i386
-------------------------------------+-------------------------------------
Reporter: cheuberg | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.9
Component: packages: | Resolution:
standard | Merged in:
Keywords: mpir | Reviewers:
Authors: Clemens Heuberger | Work issues:
Report Upstream: N/A | Commit:
Branch: u/cheuberg/mpir- | 0d48fb57205cb16d58380c9b022c39eb354c3a58
bug | Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by leif):
Replying to [comment:9 leif]:
> Not ad hoc, otherwise I would have been more precise... ;-)
>
> FWIW, `__i386__` is slightly ''compiler''-dependent, so would suffice
for our purpose (i.e., GCC).
Since most of the architecture-specific stuff is managed via different
files and symlinks to them created by `configure`, there's no straight-
forward "MPIR equivalent".
We could use `defined(__i386__) || defined(__i386)` (the latter is used by
at least M$), and probably to be triple-safe also check whether
`GMP_LIMB_BITS` is really 32 (I vaguely remember ''some''^TM^ ill compiler
used to define ''both'' `__i386__` ''and'' `__x86_64__` on x86_64, but I'm
not sure).
I don't think it really matters as long as our fix works for the
architectures supported by Sage, as we're not going to submit the patch
upstream.
--
Ticket URL: <http://trac.sagemath.org/ticket/19280#comment:10>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
