From: malc <malc@pulsesoft.com>
To: spetreolle@users.sourceforge.net, qemu-devel@nongnu.org
Subject: Re: RE : [Qemu-devel] cvttps2dq, movdq2q, movq2dq incorrect behaviour
Date: Tue, 20 Jun 2006 17:51:17 +0400 (MSD) [thread overview]
Message-ID: <Pine.LNX.4.64.0606201750190.2310@home.oyster.ru> (raw)
In-Reply-To: <20060620131539.71677.qmail@web26805.mail.ukl.yahoo.com>
On Tue, 20 Jun 2006, Sylvain Petreolle wrote:
> --- Julian Seward <jseward@acm.org> a ?crit :
>>
>> The SSE2 instructions cvttps2dq, movdq2q, movq2dq do not behave
>> correctly, as shown by the attached program. It should print
>>
>> cvttps2dq_1 ... ok
>> cvttps2dq_2 ... ok
>> movdq2q_1 ... ok
>> movq2dq_1 ... ok
>>
>>
>
> I tried your program on my linux station :
> CPU: AMD Athlon(tm) XP 1600+ stepping 02
>
> [syl@wine qemu]$ gcc --version
> gcc (GCC) 4.1.1 20060525 (Red Hat 4.1.1-1)
>
> [syl@wine qemu]$ gcc -msse2 sse2test.c -o sse2test
> [syl@wine qemu]$ ./sse2test
> cvttps2dq_1 ... failed
> cvttps2dq_2 ... failed
> movdq2q_1 ... failed
> movq2dq_1 ... failed
>
> what am i doing wrong here ?
Running it on a CPU without SSE2, if i'm allowed to venture a gues.
--
mailto:malc@pulsesoft.com
next prev parent reply other threads:[~2006-06-20 13:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 10:54 [Qemu-devel] cvttps2dq, movdq2q, movq2dq incorrect behaviour Julian Seward
2006-06-20 11:29 ` malc
2006-06-20 11:48 ` Julian Seward
2006-06-20 14:26 ` malc
2006-06-21 0:31 ` Julian Seward
2006-06-21 8:21 ` malc
2006-06-21 11:04 ` malc
2006-06-21 23:01 ` Julian Seward
2006-06-20 13:15 ` RE : " Sylvain Petreolle
2006-06-20 13:51 ` malc [this message]
2006-06-20 14:13 ` Julian Seward
2006-06-20 15:06 ` RE : " Sylvain Petreolle
2006-06-20 15:14 ` Guillaume POIRIER
2006-06-20 14:17 ` RE : " Jens Axboe
2006-06-20 14:23 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0606201750190.2310@home.oyster.ru \
--to=malc@pulsesoft.com \
--cc=qemu-devel@nongnu.org \
--cc=spetreolle@users.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).