From: "H. J. Lu" <hjl@lucon.org>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: rdunlap@xenotime.net, gcc@gcc.gnu.org,
libc-alpha@sources.redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Change x86 prefix order
Date: Wed, 6 Dec 2006 10:00:47 -0800 [thread overview]
Message-ID: <20061206180047.GA810@lucon.org> (raw)
In-Reply-To: <200612061752.kB6Hqd1J004450@harpo.it.uu.se>
On Wed, Dec 06, 2006 at 06:52:39PM +0100, Mikael Pettersson wrote:
>
> If hardware x86 decoders (i.e., Intel or AMD processors)
> get measurably faster with the new order, that would be
> a good reason to change it.
I was told that AMD processors had no preferences and Intel processors
preferred the proposed order.
H.J.
next prev parent reply other threads:[~2006-12-06 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 17:52 Change x86 prefix order Mikael Pettersson
2006-12-06 18:00 ` H. J. Lu [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-06 7:00 H. J. Lu
2006-12-06 16:43 ` Randy Dunlap
2006-12-06 17:00 ` H. J. Lu
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=20061206180047.GA810@lucon.org \
--to=hjl@lucon.org \
--cc=gcc@gcc.gnu.org \
--cc=libc-alpha@sources.redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=rdunlap@xenotime.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