On Feb 26, 10:24 am, Jason <ja...@njkfrudils.plus.com> wrote: > Hi > > An outline of what I hope we can do for MPIR v2.4 > > 1) Release on June 1st > > 2) More x86_64 assembler code > > 3) Clean-ups > > 4) Bill's new FFT > > 5) Test scripts to include apps ie MPFR,ECM,PARI,FLINT etc > > 6) Split up longlong.h into arch's > > 7) upgrade to latest autotools as skynet doesn't have the version we use , > this could fix a few minor problem we have currently. > > 8) MSVC cmd line build using existing VS2010 projects , it nearly works > already , the cmd line build which just uses CL.EXE and LINK.EXE is another > matter and related to task 9) below. > > 9) Python code for cpu path selection , to share between autotools and MSVC , > MSVC builds would then only need one project?. > > 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) , we have some of this already , do more. > > 11) try autoupdate: which updates configure.in to the latest spec , there > appear to be some windows dll updates. > > 12) Clean up the ABI selection code and the compiler selection code , just > stick to system defaults > > 13) Get the demo's onto the website > > 14) Update website , as some of it a bit out of date > > I doubt all of these will get done :) > > Any comments or suggestions or volunteers ? > > Thanks > Jason
15) Test scripts to "fake" cpus we dont have on OSes we do , ie atom on windows 16) Automate more of the testing procedure , a complete test on sage cluster , skynet , gcc-farm and homenet takes me at least 2+ hours just to login and start the scripts and report the results 17) disconnect tests from the terminal , so I'm not stuck in one OS while they are running 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-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.
