This is the masm? assembler movd/movq mix up.
Fixed in svn.

----- Original Message ----- 
From: "Jeff Gilchrist" <jeff.gilchr...@gmail.com>
To: <mpir-devel@googlegroups.com>
Sent: Thursday, October 15, 2009 6:22 PM
Subject: [mpir-devel] Re: MPIR 1.3 (jumbo release) available for testing.... 
at last


>
> On Thu, Oct 15, 2009 at 1:13 AM, Bill Hart <goodwillh...@googlemail.com> 
> wrote:
>
>> I've just put up MPIR 1.3 (alpha) for testing.
>
> I should be able to do the Windows 64bit tests tonight.
>
> Tests that have passed:
>
> - Core2, Vista 32bit, cygwin gcc 3.4.4:  ./configure; make; make check
> - Core2, Vista 32bit, VS2008 Express SP1: build mpir.sln; build
> mpir-tests.sln; run-tests.py
> - Pentium-D, XP 32bit, cygwin gcc 3.4.4:  ./configure; make; make check
> - Pentium-D, XP 32bit, VS2008 SP1: build mpir.sln; build
> mpir-tests.sln; run-tests.py
> - Xeon E5440, Linux 2.6 64bit, gcc 4.1.2:  ./configure; make; make check
>
> Tests that failed:
>
> - Itanium2 with icc (already mentioned in known issues)
> - Opteron 248, Linux 2.6 64bit, gcc 3.4.6:  ./configure; make
>
> m4  -DHAVE_CONFIG_H -D__GMP_WITHIN_GMP -DOPERATION_rshift -DPIC
> rshift.asm >tmp-rshift.s
> gcc -std=gnu99 -c -DHAVE_CONFIG_H -O2 -m64 -march=k8 -mtune=k8
> -D__GMP_WITHIN_GMP -I.. -DOPERATION_rshift -I. -I. -I.. tmp-rshift.s
> -fPIC -DPIC -o .libs/rshift.o
> tmp-rshift.s: Assembler messages:
> tmp-rshift.s:52: Error: suffix or operands invalid for `movq'
> tmp-rshift.s:55: Error: suffix or operands invalid for `movq'
> tmp-rshift.s:63: Error: suffix or operands invalid for `movq'
> make[2]: *** [rshift.lo] Error 1
>
> Jeff.
>
> > 


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to