#13947: zn_poly segfaults during tuning and tests on OS X and Cygwin when built 
on
a busy system
-------------------------------------------+--------------------------------
       Reporter:  jpflori                  |         Owner:  tbd     
           Type:  defect                   |        Status:  new     
       Priority:  major                    |     Milestone:  sage-5.6
      Component:  packages                 |    Resolution:          
       Keywords:  zn_poly spkg cygwin osx  |   Work issues:          
Report Upstream:  N/A                      |     Reviewers:          
        Authors:                           |     Merged in:          
   Dependencies:                           |      Stopgaps:          
-------------------------------------------+--------------------------------

Comment (by leif):

 Replying to [comment:16 leif]:
 > Replying to [comment:15 leif]:
 > > The offending parameter in John's `tuning.c` seems to be
 `tuning_info[62].mul_fft_thresh` (=90, which is extraordinarily low),
 i.e., that's the one that (for me) causes the `nuss_mul()` test failures
 here.
 >
 > When I set all `mul_fft_thresh`s to 1, I get a lot more failures
 (although not all tests/comparisons fail).
 >
 > More interestingly, the failures only happen when squaring.

 I also get the quick test to fail with all (2...64 bits) `mul_fft_thresh`
 entries set to 1.

 And I meanwhile managed to get "invalid" tuning parameters on Linux
 x86_64, too (although just once, but unintentionally).

 I don't think the bug (or test failure) is in any way related to the
 compiler / GCC version or compilation options, as I've so far been able to
 force it with every GCC version I tried (4.4.3, 4.6.3, 4.7.0, 4.7.2),
 regardless of whether I used e.g. `-O0` or `-O3`, or `-fno-strict-
 aliasing`.

 Still don't know whether (just) `testcase_nuss_mul()` is broken (in
 violating preconditions by using the same array for both [identical]
 operands when squaring [`sqr==1`], although assertion checking is enabled
 when compiling for the `test` program), or whether it actually triggers a
 real bug by doing so.  Someone more knowledgable than me should probably
 check this.

 [As mentioned, all failures vanish when `buf1 != buf2`, i.e., when they
 don't alias even if `sqr==1`.]

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