From: "H. J. Lu" <hjl@lucon.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: gcc@gcc.gnu.org, GNU C Library <libc-alpha@sources.redhat.com>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Change x86 prefix order
Date: Wed, 6 Dec 2006 09:00:30 -0800 [thread overview]
Message-ID: <20061206170030.GA543@lucon.org> (raw)
In-Reply-To: <20061206084317.4c0ef28d.rdunlap@xenotime.net>
On Wed, Dec 06, 2006 at 08:43:17AM -0800, Randy Dunlap wrote:
> On Tue, 5 Dec 2006 23:00:14 -0800 H. J. Lu wrote:
>
> > On x86, the order of prefix SEG_PREFIX, ADDR_PREFIX, DATA_PREFIX and
> > LOCKREP_PREFIX isn't fixed. Currently, gas generates
> >
> > LOCKREP_PREFIX ADDR_PREFIX DATA_PREFIX SEG_PREFIX
> >
> > I will check in a patch:
> >
> > http://sourceware.org/ml/binutils/2006-12/msg00054.html
> >
> > tomorrow and change gas to generate
> >
> > SEG_PREFIX ADDR_PREFIX DATA_PREFIX LOCKREP_PREFIX
>
> Hi,
> Could you provide a "why" for this in addition to the
> "what", please?
LOCKREP_PREFIX is also used as SIMD prefix. DATA_PREFIX can be used as
either SIMD prefix or data size prefix for SIMD instructions. The new
order
SEG_PREFIX ADDR_PREFIX DATA_PREFIX LOCKREP_PREFIX
will make SIMD prefixes close to SIMD opcode.
H.J.
next prev parent reply other threads:[~2006-12-06 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 7:00 Change x86 prefix order H. J. Lu
2006-12-06 16:43 ` Randy Dunlap
2006-12-06 17:00 ` H. J. Lu [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-06 17:52 Mikael Pettersson
2006-12-06 18: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=20061206170030.GA543@lucon.org \
--to=hjl@lucon.org \
--cc=gcc@gcc.gnu.org \
--cc=libc-alpha@sources.redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.