On Jun 9, 1:41 pm, Jason <ja...@njkfrudils.plus.com> wrote: > On Thursday 09 June 2011 13:37:39 Jason wrote: > > > > > Hi > > > Now that 2.4 is almost ready to go , here's some ideas for mpir-2.5 > > > 1) Release on 1st September > > > 2) upgrade internals if needed ie yasm,autotools,gnu config > > > 3) New x64 assembler code > > > 4) remove explicit support for old cpus sh,m68k,alpha? > > > 5) General cleanups > > > 6) finish msvc cl build , it mostly works and improve the flags , compiler > > detection, ABI selection > > > 7) improve test scripts , add more OSes,cpu's and apps and combinations > > > 8) improve automation ie devel/regen script > > > 9) Cleanup the ABI selection , use autotools default > > > 10) Cleanup compiler selection , use autotools default , not sure about > > this > > > 11) New FFT by Bill > > > 12) Yasm to assemble all asm files , just need to get it to work in a FAT > > build > > > 13) Now we have split longlong , optimize it , use compiler intrinsics or > > even plain C? > > > 14) a fake windows build in linux (and vice versa) , so that tests and > > timings can be done in the other ABI. > > Timings should be easier , just prefix the RDTSC with code to swap the > > params , and similarly for make check stuff. There will be some > > difficulties eg if asm in linux uses the red-zone , or doesn't confirm > > to the windows stack usage , although as we are only interested in > > timings , this might not be a problem. > > > 15) try autoupdate: which updates configure.in to the latest spec , there > > appear to be some windows dll updates. > > > 16) remove all this stuff HAVE HOST _CPU_x86 powerpc etc , not needed now > > > 17) remove all the preinv special cases , cant do this until 18) is done , > > and need to leave a compatibility layer behind > > > 18) New consistent division interface and code > > > 19) Come up with a general solution to functions which have two entry > > points > > > 20) One file = one function , file name = function name > > > 21) get rid of special case code for old systems , it complicates the build > > no end , at the moment development time is a more precious resource than > > corner case code speed > > > 22) Make sure all corner cases are tested in mpz etc > > > Jason > > and > > 23) More mpz_*_ux/sx functions
24) New Toom22 code , the new code is smaller if we let the high part >= low part which is the opposite of the current code , so it's probably easier just to rewrite the whole thing. -- 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.
