Not in the published divide-and-conquer algorithm, no. There was a bug in the implementation of the new basecase algorithm, which was not published, nor very important. On most machines it was switched off. And even on the machines where it was used (with the exception of itanium where it seemed to be used a lot), it was only used for *very* small operands.
I'm slightly surprised that there was a bug, since I literally ran tests for hours to check it. But it's simply not worth debugging to find the exact cause. The whole thing can be ditched without anyone really noticing anything, performance-wise. If I had more time I'd be more thorough with the postmortem, but right at the moment there are infinitely many, infinitely more important things I must be getting on with. Bill. On 13 November 2015 at 18:34, Jean-Pierre Flori <jpfl...@gmail.com> wrote: > Hi Bill, > > Do you mean there was an issue in your new division algorithm? > > Best, > JP > > -- > You received this message because you are subscribed to the Google Groups > "mpir-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to mpir-devel+unsubscr...@googlegroups.com. > To post to this group, send email to mpir-devel@googlegroups.com. > Visit this group at http://groups.google.com/group/mpir-devel. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to mpir-devel+unsubscr...@googlegroups.com. To post to this group, send email to mpir-devel@googlegroups.com. Visit this group at http://groups.google.com/group/mpir-devel. For more options, visit https://groups.google.com/d/optout.
