On Wed, Jun 9, 2010 at 12:29 PM, Minh Nguyen <[email protected]> wrote: > Hi folks, > > MPIR 2.1.1-rc1 was released on 09th June 2010. > > * source: http://www.mpir.org/mpir-2.1.1-rc1.tar.gz > * documentation: http://www.mpir.org/mpir-2.1.1.pdf > > This RC affects only the Windows platform. We would appreciate any > help with testing the RC on Windows. In any case, please test and > report all issues. > > The main change in this release cycle is: > > * Fixed a long standing but latent bug in some Windows assembler code > that has only now been triggered because of recent changes in higher > level code. In outline the K8/K10 mpn_sublsh_n function entry point > (in the file mpn/x86_64w/k8/sublsh_n.asm) was not being set up > correctly. Thanks to Case Vanhorsen for reporting this bug. > > -- > Regards > Minh Van Nguyen > > -- > You received this message because you are subscribed to the Google Groups > "mpir-devel" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/mpir-devel?hl=en. > >
The command line build for --cpu-k8 now works properly. The command line build for --cpu-k10 still fails for a different reason. Looking in lib_mpri_k10.vcproj, it appears that VCPreBuildEventTool tries to copy gmp-mparam.h from ..\..\mpn\x86_64w\k10\ but that file is actually located in ..\..\mpn\x86_64w\k8\k10\. I change the project file to reflect the correct location and compilation was successful. "make check" failed for popcount and hamdist but since I actually have a core2 CPU and popcount and hamdist both have K10 specific assembly, I'm not surprised the tests failed. I don't have easy access to a K8 or K10 so I can't test on the correct processor. casevh -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
