From: "H. J. Lu" <hjl@lucon.org>
To: linux-os <linux-os@analogic.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
binutils@sources.redhat.com, Andi Kleen <ak@muc.de>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: i386/x86_64 segment register issuses (Re: PATCH: Fix x86 segment register access)
Date: Thu, 31 Mar 2005 12:00:00 -0000 [thread overview]
Message-ID: <20050330211102.GB15384@lucon.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0503301120130.27995@chaos.analogic.com>
On Wed, Mar 30, 2005 at 11:23:25AM -0500, linux-os wrote:
>
> So if there are any "movw (mem), %ds" and
> "movw %ds, (mem)" in the code. The sizeof(mem)
> needs to be 32-bits and the 'w' needs to be removed.
> Otherwise, we are wasting CPU cycles and/or fooling
> ourselves. GAS needs to continue to generate whatever
> it was fed, with appropriate diagnostics if it
> is fed the wrong stuff.
FYI, gas hasn't generated 0x66 on "movw (%eax),%ds" for a long time
and started doing it on "movw %ds,(%eax)" since Nov. 4, 2004.
H.J.
next prev parent reply other threads:[~2005-03-30 21:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 23:31 PATCH: Fix x86 segment register access H. J. Lu
2005-03-28 10:21 ` i386/x86_64 segment register issuses (Re: PATCH: Fix x86 segment register access) H. J. Lu
2005-03-30 9:46 ` PATCH: i386/x86_64 segment register access update H. J. Lu
[not found] ` <m14qev3h8l.fsf@muc.de>
[not found] ` <Pine.LNX.4.58.0503291618520.6036@ppc970.osdl.org>
[not found] ` <20050330015312.GA27309@lucon.org>
[not found] ` <Pine.LNX.4.58.0503291815570.6036@ppc970.osdl.org>
[not found] ` <20050330040017.GA29523@lucon.org>
2005-03-30 22:19 ` i386/x86_64 segment register issuses (Re: PATCH: Fix x86 segment register access) Linus Torvalds
2005-03-30 23:24 ` linux-os
2005-03-31 12:00 ` H. J. Lu [this message]
2005-03-31 8:55 ` H. J. Lu
2005-03-31 13:27 ` Pau Aliagas
2005-03-31 15:05 ` H. J. Lu
2005-03-31 15:05 ` Pau Aliagas
2005-03-31 15:07 ` H. J. Lu
2005-03-31 15:37 ` Andi Kleen
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=20050330211102.GB15384@lucon.org \
--to=hjl@lucon.org \
--cc=ak@muc.de \
--cc=binutils@sources.redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=torvalds@osdl.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 read-only IMAP folder(s) and NNTP newsgroup(s).