I'd like to propose a code freeze on all K8/K10 assembly code, which I have now converted to yasm format, unless serious bugs are uncovered.
If we freeze the code then we can begin testing. I propose we wear out each and every file with /tests/devel/try including many small operands and as many different types of data as try can throw at it. On my machine the K8 code gets a bench of 15283 which is what it got before the conversion. Also on K10 I did cycle timings of all the functions we care about and they did not change (to within tolerances due to variations between runs of course). I'm inclined to finish the core 2 code conversion tomorrow, do some cleaning up of the C code (insert some whitespace :-)) and then release 1.0.0. It's just about as much work as releasing 0.9.1. By the way, make check still runs the yasm tests. Bill. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
