#11705: Port Sage to SUSE Linux Power 7 (ppc64).
-------------------------------+--------------------------------------------
       Reporter:  was          |         Owner:  drkirkby
           Type:  enhancement  |        Status:  new     
       Priority:  major        |     Milestone:  sage-5.0
      Component:  porting      |    Resolution:          
       Keywords:  sd32 sd35.5  |   Work issues:          
Report Upstream:  N/A          |     Reviewers:          
        Authors:               |     Merged in:          
   Dependencies:               |      Stopgaps:          
-------------------------------+--------------------------------------------

Comment (by zimmerma):

 I have spent several hours on this and my conclusion is that the culprit
 is Sage (i.e. Cython).
 In {{{real_mpfi.pyx}}} one can read:
 {{{
             elif PY_TYPE_CHECK(a, Rational) and PY_TYPE_CHECK(b,
 Rational):
                 rat = a
                 rat1 = b
                 # todo: The <object> coerce is evidently to get around a
 weird bug in SageX (?)
                 mpfi_interv_q(self.value, <object>rat.value,
 <object>rat1.value)
 }}}
 and the same coerce is done in the integer case.

 I am 99% sure that we hit that weird bug. Indeed with {{{RIF(1,1)}}} the
 integers (mpz_t) which are
 passed to {{{mpfi_interv_z}}} are malformed, with {{{SIZ=2}}} instead of
 {{{SIZ=1}}}.

 However I have no idea how to solve that weird bug, or how to find another
 workaround.
 Can we know who did write this comment?

 It might be that the issue is related to the fact that the Power7 is big
 endian.
 Was Sage tested on other 64-bit big endian platforms?

 Paul

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11705#comment:63>
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.

Reply via email to