Re: [Mingw-w64-public] Problem with gmp-ecm and mingw64...

2012-02-22 Thread David Cleaver
Thank you for giving me suggestions of things to try. I have tried pushing and popping r8,r9,r10,r11,rcx, and rdx. However, this did not change the behavior of the program. I looked at the documentation you mentioned and they seem to say that r10/r11 should be considered volatile (ie, destroy

Re: [Mingw-w64-public] Problem with gmp-ecm and mingw64...

2012-02-22 Thread Kai Tietz
Thanks for the link. The issue you see is caused by register-clobbering of r10/r11 etc. Those are callee saved-registers. So you need to save them too. By adding following lines (without the +): GSYM_PREFIX`'ecm_redc3: push%rbp# Push registers

Re: [Mingw-w64-public] Problem with gmp-ecm and mingw64...

2012-02-20 Thread David Cleaver
Hello, The file that I think may be causing problems does not contain inline assembler, it is a straight assembly file (redc.asm). I do not see any inline assembly in gmp-ecm. One strange thing I see at the top of that file is the following: # void ecm_redc3(mp_limb_t * z, const mp_limb_t * x

Re: [Mingw-w64-public] Problem with gmp-ecm and mingw64...

2012-02-19 Thread Kai Tietz
Hi, such failures a commonly caused by inline-assembler not treating memory-ref proper. I assume that inline assembler doesn't specify explicit memory-clobber/modify. Newer gcc versions are here more strict then older versions. Kai 2012/2/20 David Cleaver : > Hello everyone, > > I have run int

[Mingw-w64-public] Problem with gmp-ecm and mingw64...

2012-02-19 Thread David Cleaver
Hello everyone, I have run into a very strange problem and I am not sure what might be causing it. I am compiling the latest svn of gmp-ecm (right now it is 1746) and depending on whether I insert a few extra print statements or not, one certain test in gmp-ecm will either run to completion or