#9703: Doctest failures caused by non-working sympow on 32-bit Solaris x86 and
32-bit OpenSolaris
------------------------+---------------------------------------------------
   Reporter:  drkirkby  |       Owner:  GeorgSWeber
       Type:  defect    |      Status:  new        
   Priority:  major     |   Milestone:  sage-4.5.3 
  Component:  build     |    Keywords:             
     Author:            |    Upstream:  N/A        
   Reviewer:            |      Merged:             
Work_issues:            |  
------------------------+---------------------------------------------------
Description changed by drkirkby:

Old description:

> John Palmieri has built most of Sage on the host fulvia, but there are a
> number of tests related to sympow that are failing. The summary at the
> end shows:
>

> {{{
> The following tests failed:
> <snip>
>         sage -t  -long devel/sage/sage/lfunctions/sympow.py # 13 doctests
> failed
> <snip>
> Total time for all tests: 7305.2 seconds
> }}}
>
> Looking at the source code, it is not valid C, so it's quite possible the
> code gets mis-compiled. In fact, IMHO, gcc should reject the code - just
> as the Sun compiler does.
>
> I'll try to work out what was intended and see if the code can be re-
> written in a way that compiles with the Sun compiler, in which case gcc
> should have more chance of generating correct code.

New description:

 John Palmieri has built most of Sage on the host fulvia, but there are a
 number of tests related to sympow that are failing. The summary at the end
 shows:

 {{{
 The following tests failed:
 <snip>
         sage -t  -long devel/sage/sage/lfunctions/sympow.py # 13 doctests
 failed
 <snip>
 Total time for all tests: 7305.2 seconds
 }}}

 Looking at the source code, it is not valid C, so it's quite possible the
 code gets mis-compiled. In fact, IMHO, gcc should reject the code - just
 as the Sun compiler does.

 I'll try to work out what was intended and see if the code can be re-
 written in a way that compiles with the Sun compiler, in which case gcc
 should have more chance of generating correct code.

--

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