From mboxrd@z Thu Jan  1 00:00:00 1970
References: <c4aef31952842c126252639a8c6bf4fb@brasstown.quanstro.net>
	<5A4C08F0-FE7C-403F-8F66-69D3AAF440A0@gmail.com>
	<17256729babb13da75a585c6bdd97898@brasstown.quanstro.net>
From: Don Bailey <don.bailey@gmail.com>
Content-Type: text/plain;
	charset=us-ascii
In-Reply-To: <17256729babb13da75a585c6bdd97898@brasstown.quanstro.net>
Message-Id: <08CDC323-1752-4C46-B518-ADF3C38E18DB@gmail.com>
Date: Sun,  8 Feb 2015 17:50:09 -0700
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: [9fans] cmovne
Topicbox-Message-UUID: 437a4aac-ead9-11e9-9d60-3106f5b1d025

Ahh gotcha.=20



> On Feb 8, 2015, at 4:37 PM, erik quanstrom <quanstro@quanstro.net> wrote:
>=20
>> On Sun Feb  8 15:31:26 PST 2015, don.bailey@gmail.com wrote:
>> Technically, there are a few instructions that the 9 compilers miss.
>> This is generally handled by the BYTE directive (see the asm manual).
>>=20
>> Alternatively, adding a new instruction to the lexer/etc is fairly
>> trivial.  See diffs between vc and kc, for example.
>=20
> you can't actually sneak around the linker with BYTE.  try it, you'll see.=

>=20
> i've added many instructions to the various compilers.  i'm just double ch=
ecking
> that it is indeed a valid instruction.  the manual says it is, but that's s=
ubject
> to my reading comprehension.  :-)
>=20
> - erik
>=20