All of lore.kernel.org
 help / color / mirror / Atom feed
From: hpa@zytor.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: Intel vs AMD64
Date: Fri, 27 Feb 2004 18:44:00 +0000 (UTC)	[thread overview]
Message-ID: <c1o35g$ii7$1@terminus.zytor.com> (raw)
In-Reply-To: 20040226133959.GA19254@dingdong.cryptoapps.com

Followup to:  <20040226133959.GA19254@dingdong.cryptoapps.com>
By author:    Chris Wedgwood <cw@f00f.org>
In newsgroup: linux.dev.kernel
> 
> Not that it really matters that much --- but I'm curious to know why
> Intel made this decision?
> 
> It seems really dumb to make such differences when Intel is already
> sorely lagging behind their competitor here, I would think given the
> circumstances Intel would try to be as compatible as possible on all
> fronts.

This, and a whole bunch of the other "IA-32e differences", I think
really should be classified as "Intel bugs."

They really have more the flavour of errata than anything else...

	-hpa

  parent reply	other threads:[~2004-02-27 18:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-26  5:32 Intel vs AMD64 Nakajima, Jun
2004-02-26 13:39 ` Chris Wedgwood
2004-02-26 14:35   ` Richard B. Johnson
2004-02-26 19:25     ` Timothy Miller
2004-02-26 19:46       ` Richard B. Johnson
2004-02-27 18:44   ` H. Peter Anvin [this message]
2004-02-26 19:18 ` Timothy Miller
2004-02-26 19:45   ` Scott Robert Ladd
2004-02-27 14:43     ` Timothy Miller
2004-03-03 17:34   ` Pavel Machek
     [not found] <7F740D512C7C1046AB53446D37200173EA28A5@scsmsx402.sc.intel.com.suse.lists.linux.kernel>
     [not found] ` <403E4681.20603@techsource.com.suse.lists.linux.kernel>
2004-02-26 20:17   ` Andi Kleen
2004-02-27 14:50     ` Timothy Miller
  -- strict thread matches above, loose matches on Subject: below --
2004-02-26  4:28 richard.brunner

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='c1o35g$ii7$1@terminus.zytor.com' \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.