From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Fri, 17 Jan 2014 15:40:52 -0500
To: 9fans@9fans.net
Message-ID: <9b21d3bc79832cd1d1d21b1caab10f35@ladd.quanstro.net>
In-Reply-To: <16c90927387c0a9664e3f4c14e0736b3@felloff.net>
References: <16c90927387c0a9664e3f4c14e0736b3@felloff.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] MOVLQSX wrong operand order
Topicbox-Message-UUID: b3ca396c-ead8-11e9-9d60-3106f5b1d025

On Fri Jan 17 15:09:33 EST 2014, cinap_lenrek@felloff.net wrote:
> just disassembled some code generated by 6c
> and found something funny. the debugger seems
> to print the operands of MOVLQSX in the wrong
> order.

there may be more of these.  maybe if , were replaced with =E2=86=92 ....

- erik