From: "Jeebs" <jeebs@yango.us>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] x86_64 target
Date: Wed, 5 Jan 2005 11:48:13 -0600 [thread overview]
Message-ID: <008001c4f34e$be22b200$ad4aa50c@computername> (raw)
In-Reply-To: 200501041429.51792.paul@codesourcery.com
From: "Paul Brook"
> On Tuesday 04 January 2005 02:15, Karl Magdsick wrote:
>> The EMT Xeons implement all of the amd64 instructions that were in an
>> early release of the instruction set reference, so I think a single
>
> The Intel chips actually implement all the instructions except 3DNOW and add
> SSE3, same as p4 vs. AthlonXP. These are the only instruction set
> differences, and the only differences that are visible from userspace.
Actually, I thought the Intel chips did *not* implement the full x86-64 instruction set. That's what a few early reports were saying.
They made their 64 bit version using a draft of the initial 64 bit specs, but AMD made some changes right at the end, and as a result the Intel chips (and AMD's own initial batch of chips) don't fully support the x86-64 instruction set.
I haven't been keeping track, but I haven't heard of any changes from Intel to implement the missing instruction(s).
next prev parent reply other threads:[~2005-01-05 18:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 0:18 [Qemu-devel] x86_64 target Fabrice Bellard
2005-01-04 2:15 ` Karl Magdsick
2005-01-04 14:29 ` Paul Brook
2005-01-05 17:48 ` Jeebs [this message]
2005-01-04 6:31 ` [Qemu-devel] " Alexander E. Patrakov
2005-01-04 19:56 ` Fabrice Bellard
2005-01-06 12:10 ` [Qemu-devel] " Lennert Buytenhek
2005-01-06 12:42 ` Lennert Buytenhek
2005-01-17 17:54 ` [Qemu-devel] " Ronald
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='008001c4f34e$be22b200$ad4aa50c@computername' \
--to=jeebs@yango.us \
--cc=qemu-devel@nongnu.org \
/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).