From: "H. J. Lu" <hjl@lucon.org>
To: Pau Aliagas <linuxnow@newtral.org>
Cc: Andi Kleen <ak@muc.de>,
linux kernel <linux-kernel@vger.kernel.org>,
binutils@sources.redhat.com
Subject: Re: i386/x86_64 segment register issuses (Re: PATCH: Fix x86 segment register access)
Date: Wed, 30 Mar 2005 16:34:37 -0800 [thread overview]
Message-ID: <20050331003437.GB19573@lucon.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0503310015490.7060@pau.intranet.ct>
On Thu, Mar 31, 2005 at 12:18:55AM +0200, Pau Aliagas wrote:
> On Wed, 30 Mar 2005, H. J. Lu wrote:
>
> >On Wed, Mar 30, 2005 at 07:57:28AM -0800, Linus Torvalds wrote:
>
> >>>There is no such an instruction of "movl %ds,(%eax)". The old assembler
> >>>accepts it and turns it into "movw %ds,(%eax)".
> >>
> >>I disagree. Violently. As does the old assembler, which does not turn
> >>"mov" into "movw" as you say. AT ALL.
> >
> >I should have made myself clear. By "movw %ds,(%eax)", I meant:
> >
> > 8c 18 movw %ds,(%eax)
> >
> >That is what the assembler generates, and should have generated, for
> >"movw %ds,(%eax)" since Nov. 4, 2004.
>
> Could this be the reason for the reported slowdown in the last six months?
>
Can you elaborate?
H.J.
next prev parent reply other threads:[~2005-03-31 0:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050326020506.GA8068@lucon.org>
2005-03-27 22:24 ` i386/x86_64 segment register issuses (Re: PATCH: Fix x86 segment register access) H. J. Lu
2005-03-28 15:47 ` Andi Kleen
2005-03-28 17:46 ` H. J. Lu
2005-03-28 18:22 ` H. J. Lu
2005-03-30 0:30 ` Linus Torvalds
2005-03-30 1:53 ` H. J. Lu
2005-03-30 2:44 ` Linus Torvalds
2005-03-30 4:00 ` H. J. Lu
2005-03-30 15:57 ` Linus Torvalds
2005-03-30 16:23 ` linux-os
2005-03-30 21:11 ` H. J. Lu
2005-03-30 21:08 ` H. J. Lu
2005-03-30 22:18 ` Pau Aliagas
2005-03-31 0:34 ` H. J. Lu [this message]
2005-03-31 0:57 ` Pau Aliagas
2005-03-31 1:52 ` H. J. Lu
2005-03-31 10:19 ` Andi Kleen
2005-03-30 15:25 ` Andi Kleen
2005-03-29 19:17 ` PATCH: i386/x86_64 segment register access update 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=20050331003437.GB19573@lucon.org \
--to=hjl@lucon.org \
--cc=ak@muc.de \
--cc=binutils@sources.redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxnow@newtral.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.