Hi Hopefully we can release mpir-2.1.1 today , then this is what I plan to do. I dont have a lot of time in the next month so I'll will mainly concentrate on small items ie bug fixing/cleaning-up , stuff I can do in a few hours or in fits and starts , nothing where I have to sit down for a day or two :(
On Jun 2, 10:18 pm, Jason Moxham <ja...@njkfrudils.plus.com> wrote: > Hi , here are some thoughts about what we should/could do for the next > release. > > 1) Upgrade yasm to the latest (easy) Yes > > 2) Upgrade gnu config to the latest ( dont know how difficult that is , but it > could fix some niggles we have , and it might simplify our specialisations. > > 3) Upgrade to the latest autotools/libtool ( some distros are moving over to > the latest 2.2 , we may need/want to do the same , again dont know what this > involves) > > 4) A few assembler functions to add > Yes > 5) Move demo's out of the library onto the web page > Yes > 6) Get rid of ancient cpus/compilers ( we will still work under C , if anyone > cares) , this would simplify configure a bit , cray,pyramid, > z8000,list,clipper,.... > Yes These chips a29k clipper i960 m88k ns32k pyr z8000 z8000x are not supported in the current GCC so I will remove asm code and all the configure bumf that goes with it. Also maybe vax and cray(old non ieee standard) , also the lisp directory should be on the website , not in the library. There is also some configure guff for cpu's which have already been removed , clean all this up. > 7) Make configure run faster , I'm sure we can remove some of the tests , I > can't believe they are still needed , and/or share the test results with yasm. > > 8) make make check parallel , it can be done. > > 9) Some of the changes we have made , have not been finished , finish them. > > 10) Split configure into two , ie standard and MPIR specific , should make the > maintenance easier , this is fairly ambitious :) > > 11) drop support for building/running on FAT file systems ( ie file name 8.3 > format) > > 12) simple command line build for windows ( not dependant of vcproj files) > > 13) fix some known bugs > Yes > 14) 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) > Yes , I'll start , and we will see how it goes Also remove the pre-build stuff , it is needlessly complicated and only really needed for nail builds , which we dont support . I'll put the files generated in the mpn/cpu/ directorys or rather links to the only two variants we support. Plenty of other little bits to do :) Jason > Some of these are trickier than others , but my aim is to simplify the system > (the non-computational parts of it) > > Bets now being taken on what % will get done :) > > Thoughts? > > 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.
