#12173: Update FLINT to 2.3
---------------------------------------------------------------------+------
       Reporter:  mhansen                                            |         
Owner:  tbd         
           Type:  enhancement                                        |        
Status:  needs_work  
       Priority:  major                                              |     
Milestone:  sage-5.8    
      Component:  packages                                           |    
Resolution:              
       Keywords:  flint spkg                                         |   Work 
issues:  OS X        
Report Upstream:  N/A                                                |     
Reviewers:  John Cremona
        Authors:  Mike Hansen, Fredrik Johansson, Jean-Pierre Flori  |     
Merged in:              
   Dependencies:  #12433                                             |      
Stopgaps:              
---------------------------------------------------------------------+------

Comment (by fredrik.johansson):

 If I'm reading this right, it prints the fmpz_poly four times before even
 entering fmpq_poly, and it's wrong the third time, that is, when calling
 (<Polynomial_integer_dense_flint>x).jprint()?

 But the fmpz coefficients are the same, so it is (seemingly) the entries
 in flint's global mpz array that are being zeroed when they shouldn't.

 It smells a lot like one of the bugs we've had in the past with the non-
 reentrant mode, i.e., somewhere, some code loads an mpz pointer, and hangs
 on to it while the mpz array gets resized. It could potentially be
 triggered by a compiler bug which, say, makes it overlook constness
 somewhere.

 You might be able to track down exactly where the mpz gets zeroed (say, by
 saving the pointer somewhere, and printing it in various places). Or,
 since the fmpz just encodes an index into the mpz array, you could perhaps
 edit the COEFF_TO_PTR macro to print the index, and find out the places
 where the particular indices of the mpzs in the coefficients of this
 polynomial are being accessed. It might also help to print where mpz array
 is being resized.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12173#comment:192>
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to