Some more idea's 14) There is some asm code out (for non-x86*) there which we can use as it is under a compatible license
15) Compilers are far more "intelligent" , the macro mul_ppmm is almost certainly faster in C (since gcc-3.4), perhaps the same for divide , although for add_ssaaaa I not at all sure , use intrinsic's and ignore crap code from old compilers. Jason On Friday 19 November 2010 10:54:44 Jason wrote: > Hi > > Now that v2.2 is almost ready for release (just waiting to test on a few > more machines ie gcc-farm , should be done by mid next week) , we should > think about what should go in to v2.3 , here are some of the things I hope > to do. > > 1) Quicker release , say no more than 3 months until release (2.1 to 2.2 > took 5.5 months. > > 2) Try the latest autotools to see if they fix a Jeff's gcc-3.4.6 problem > and the MinGW64 c++ shared make check fail > > 3) General clean-up , an endless task... > > 4) New assembler code(and some related C code) for x86_64 (*) > > 5) Try to get a complete list of cpu types for cpuid.c > > 6) Command line MSVC build > > 7) Python code for cpu path selection , to share between autotools and MSVC > , MSVC builds would then only need one project. > > 8) Some of the changes we have made , have not been finished , finish them. > (*) > > 9) Split configure into two , ie standard and MPIR specific , should make > the maintenance easier , this is fairly ambitious :) Actually I can't see > this happening at all (*) > > 10) When we update stuff , there are many places where you have to fill in > the same info , make it automatic (autotools can do this , it's just not > been set up that way) (*) > > 11) Update the test scripts to try make install(local install) so we can > build mpfr,mpc,pari,flint,(sage is too big) against the library > > 12) try autoupdate: which updates configure.in to the latest spec , there > appear to be some windows dll updates. > > 13) Clean up the ABI selection code > > > (*) is from the list of things to do in v2.2 that did not get done. > > > Any other suggestions? , or volunteers? > > Jason -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to mpir-de...@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.
