qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Guillaume POIRIER" <poirierg@gmail.com>
To: spetreolle@users.sourceforge.net, qemu-devel@nongnu.org
Subject: Re: RE : Re: [Qemu-devel] cvttps2dq, movdq2q, movq2dq incorrect behaviour
Date: Tue, 20 Jun 2006 17:14:14 +0200	[thread overview]
Message-ID: <4e03026a0606200814p68e99464j98ce627556479839@mail.gmail.com> (raw)
In-Reply-To: <20060620150631.4315.qmail@web26803.mail.ukl.yahoo.com>

Hi,

On 6/20/06, Sylvain Petreolle <spetreolle@yahoo.fr> wrote:
>
> --- Julian Seward <jseward@acm.org> a écrit :
> > >
> > > Running it on a CPU without SSE2, if i'm allowed to venture a gues.
> >
> > Yup.  Try 'strace ./sse2test' and see if it gets SIGILLs thrown at it.
> >
> > J
> >
> You are right, I get SIGILLs.
> Seems I was wrong thinking Athlon xp was able to support sse2.

Indeed. See here:
http://en.wikipedia.org/wiki/List_of_AMD_Athlon_XP_microprocessors#Athlon_XP_.22Palomino.22_.28Model_6.2C_180_nm.29

SSE2 began to be supported in AMD processors with k8/hammer/Athon64

Guillaume
-- 
"Success consists of going from failure to failure without loss of enthusiasm."
 -- Winston Churchill

  reply	other threads:[~2006-06-20 15:14 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
2006-06-20 14:13     ` Julian Seward
2006-06-20 15:06       ` RE : " Sylvain Petreolle
2006-06-20 15:14         ` Guillaume POIRIER [this message]
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=4e03026a0606200814p68e99464j98ce627556479839@mail.gmail.com \
    --to=poirierg@gmail.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).