OK, then we do need a trace of the function calls and the parameters that are passed for the failing test. Brian is probably right. It's probably an n=0 or trunc=2*n or trunc=0 passed somewhere, or something like that. I'm glad I left the code so that it doesn't deal with these cases, as it may shake some bugs out. It is very odd that it fails on such a small example though.
Bill. On 21 January 2012 17:42, Jason <ja...@njkfrudils.plus.com> wrote: > On Saturday 21 January 2012 17:37:27 Jason wrote: >> On Saturday 21 January 2012 15:33:12 Cactus wrote: >> > The FFT tuning appears to work in Windows but if I turn on asserts I see >> > the same problem that Jason reported earlier. >> > >> > But I don't see the out of memory problem. >> > >> > Brian >> > >> > >> >> with asserts on it fails make check anyway , so it's nothing to do with the >> tuning program , could be default >> parameters for the fft or something else > like the other parameters or cutoff points , this was on a sandybridge > > -- > You received this message because you are subscribed to the Google Groups > "mpir-devel" group. > To post to this group, send email to mpir-devel@googlegroups.com. > To unsubscribe from this group, send email to > mpir-devel+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/mpir-devel?hl=en. > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to mpir-devel@googlegroups.com. To unsubscribe from this group, send email to mpir-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
