From: minux <minux.ma@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] cmovne
Date: Sun, 8 Feb 2015 19:23:05 -0500 [thread overview]
Message-ID: <CA+db=n1_ZgJPA5C8k8BWszs=ObEU1BDN6+Xh=tPtR5+OuoYwrg@mail.gmail.com> (raw)
In-Reply-To: <fa4b04d61419f77f36b4709e0c503586@brasstown.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 978 bytes --]
On Sun, Feb 8, 2015 at 6:42 PM, erik quanstrom <quanstro@quanstro.net>
wrote:
> > On Sun, Feb 8, 2015 at 6:27 PM, erik quanstrom <quanstro@quanstro.net>
> > wrote:
> > > am i reading the intel docs wrong, or is 6l missing a valid
> instruction?
> > > memmove5: doasm: notfound from=12 to=92 (47) CMOVQNE DX,(DI)> >
> > Go's liblink (which is derived from [5869]l) and cmd/6a support this
> > instruction.
> does it support it with exactly that register combination?
>
No. I just realized you want conditional move from DX to (DI).
It's an illegal combination. The intel document only lists three forms for
CMOVNE:
CMOVNE r16, r/m16 // CMOVWNE
CMOVNE r32, r/m32 // CMOVLNE
CMOVNE r64, r/m64 // CMOVQNE
All of them are conditionally moving from reg/mem to a register.
(Also note the description "These instructions can move 16-bit, 32-bit or
64-bit values
from memory to a general-purpose register or from one general-purpose
register to another.")
[-- Attachment #2: Type: text/html, Size: 1580 bytes --]
next prev parent reply other threads:[~2015-02-09 0:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 23:27 erik quanstrom
2015-02-08 23:36 ` Don Bailey
2015-02-08 23:37 ` erik quanstrom
2015-02-09 0:50 ` Don Bailey
2015-02-08 23:43 ` minux
2015-02-08 23:42 ` erik quanstrom
2015-02-09 0:23 ` minux [this message]
2015-02-09 0:29 ` erik quanstrom
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='CA+db=n1_ZgJPA5C8k8BWszs=ObEU1BDN6+Xh=tPtR5+OuoYwrg@mail.gmail.com' \
--to=minux.ma@gmail.com \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).