On Saturday 09 April 2011 12:08:56 jason wrote: > On Feb 26, 11: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 > > I've had a quick go at splitting longlong into arches , and it's > pretty easy , and it does make things cleaner.For MSVC , longlong.h > would be constructed from a beginning file , the windows arch bit , > and the end file , just by concatcation. I cant see any problems with > doing it this way. By using the existing path selection mechanism we > can also get a few minor optimizations for specific cpu's. > Another point is that gmp-impl.h does have some arch specific code > (and asm code) in it , this would make most sense to move it to our > new longlong's , there is a potential problem with this , some > projects do use the internals , but they seem to use both gmp-imp.h > and longlong , and if they dont then they dont depend on the macro's > that I think we should move. This does need to be looked at for a > wider range of projects. > > > Jason
A lot of the macros in gmp-impl.h depend on the macros in longlong , so it going to be unlikely that we will have any problems. 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.
