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 >
There is a new dir for the new AMD bobcat cpu , if we cant get hold of a VIA nano , then I will make it default to the K8 code , which will be faster on average. The bocat code is an interesting mixture of code from the directorys K8,core2,nehalem and C > 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. > This is easy , I can backport this to mpir-2.2 and mpir-2.3 if needed , although the numbering convention of lib.so version numbers doesn't seem to allow such a thing !! I can also backport the correct noexecstack for x86 and the new cpu's(already done) if needed > 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 -- 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.
