On 06/03/2015 23:41, Brian Gladman wrote: > On 06/03/2015 23:12, Bill Hart wrote: >> Hi Simon, >> >> You can keep track of the ticket here: >> >> https://github.com/wbhart/mpir/issues/151 >> >> Brian is familiar with the Windows assembly code. But he doesn't develop >> for Windows. I don't know if he can assist you or not. I have added him >> in CC, just in case he can spot something. > > Hi SImon and Bill, > > Just to clarify this a bit, I don't develop for the *nix and GCC > environments on Windows (i.e. mingw/cygwin etc). > > But I do develop both C and assembler code for the native Microsoft and > Intel compilers and for the YASM assembler operating in association with > these compilers. > > I have been silent on this issue so far as it doesn't appear to impact > on the Visual Studio builds. > > But the code files being deleted to avoid the problem: > > mpn/x86_64w/core2/lshift1.asm > mpn/x86_64w/core2/rshift1.asm > > are in the Visual Studio sub-directories so we need to understand why > YASM code integrates with the Microsoft and Intel compilers but fails to > integrate correctly with GCC (unless I have misunderstood what is going on).
To be certain of this, I have just rebuilt the core2 version of MPIR with Visual Studio and confirmed that it passes all tests. The problem we now have is that it was Jason Moxham who always tested these files (that are designed specifically for use with Visual Studio) in the mingw/cygwin environments. If changes were needed he would let me know and I would adopt them if I could without messing up the Visual Studio builds. But with his passing, these files are now only being maintained for use with Visual Studio. Brian -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to mpir-devel+unsubscr...@googlegroups.com. To post to this group, send email to mpir-devel@googlegroups.com. Visit this group at http://groups.google.com/group/mpir-devel. For more options, visit https://groups.google.com/d/optout.
