On Sat, 9 Jun 2012 09:54:38 +0100 Jason Moxham <ja...@thecodecavern.co.uk> wrote:
> On Sat, 9 Jun 2012 09:14:51 +0100 > Jason Moxham <ja...@thecodecavern.co.uk> wrote: > > > This is based on the 2.5.1 branch > > Thanks Jason, I have just downloaded it and saw that it is a minor > evolution of 2.5.1. > > I assume that when 2.5.1 was branched from trunk, it worked on MSVC. > > So what matters are any post release patches for 2.5.1 and any > 2.5.1 to 2.5.2 changes. > > The only one I am aware of that caused an MSVC change in trunk was the > addition of mpn_redc_2 and, checking the 2.5.2 branch, I find that > this is not being built in the MSVC build (which presumably means > that it is not built in 2.5.1 either). > > I can't recall other MSVC issues but trunk is now very different so > its hard to be certain about this as there are too many changes when > comparing trunk with 2.5.2. This hence makes a rapid review > difficult. > So I will now update the 2.5.1 branch to add redc_2 to the MSVC build. Sorry that was a mistake - I will update the 2.5.2 branch, NOT the 2.5.1 branch > Thanks , I will also have to do the gcc-4.3.2 issue thing for all > other arches that debian supports , I think there is a general > gcc-cflags_opt that I can set , so I'll try that in trunk and 2.5.2. > Perhaps we should merge the fft branch into trunk now that Bill will > soon fill in the missing bits? I would prefer to wait until Bill does the work as quite a lot remains to be done. In particular the exp branch contains both the old and the new FFT code so it will need a big clean up after the new FFT has been completed. We also have the issue of ensuring that the new mpir_si and mpir_ui types (which allow Windows x64 to use 64-bit ints as the default) do not kill any Unix/Linux builds. Brian -- 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.
