From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CmFSs-00065j-0o for qemu-devel@nongnu.org; Wed, 05 Jan 2005 13:00:58 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CmFSr-00065X-HO for qemu-devel@nongnu.org; Wed, 05 Jan 2005 13:00:57 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CmFSr-00065U-EO for qemu-devel@nongnu.org; Wed, 05 Jan 2005 13:00:57 -0500 Received: from [24.206.159.131] (helo=smtp.cebridge.net) by monty-python.gnu.org with smtp (Exim 4.34) id 1CmFHU-0001bT-D9 for qemu-devel@nongnu.org; Wed, 05 Jan 2005 12:49:12 -0500 Message-ID: <008001c4f34e$be22b200$ad4aa50c@computername> From: "Jeebs" References: <41D9E0BB.1070202@bellard.org> <200501041429.51792.paul@codesourcery.com> Subject: Re: [Qemu-devel] x86_64 target Date: Wed, 5 Jan 2005 11:48:13 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org 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 >=20 > The Intel chips actually implement all the instructions except 3DNOW = and add=20 > SSE3, same as p4 vs. AthlonXP. These are the only instruction set=20 > 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).