Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.7.0.10 $; site ti-csl
Path: utzoo!watmath!clyde!cbosgd!ihnp4!inuxc!pur-ee!uiucdcs!convex!ti-csl!herman
From: herman@ti-csl
Newsgroups: net.micro.pc
Subject: Re: 8087 opcodes needed
Message-ID: <10200008@ti-csl>
Date: Fri, 11-Apr-86 15:00:00 EST
Article-I.D.: ti-csl.10200008
Posted: Fri Apr 11 15:00:00 1986
Date-Received: Sat, 19-Apr-86 04:04:15 EST
References: <292@cernvax.UUCP>
Lines: 21
Nf-ID: #R:cernvax.UUCP:292:ti-csl:10200008:000:704
Nf-From: ti-csl!herman    Apr 11 14:00:00 1986



Have you tried using the .8087 pseudo-op to tell Masm that you're
using 8087 opcodes?  Effective Masm 2.x, the assembler no longer
automatically recognizes 8087 opcodes.  The following should work

	.8087
	FLD	DWORD PTR [SI]

Information about the 8087 opcodes themselves can be found in the
Intel documentation.  For integer versions of 8087 commands, Microsoft
has added an "I" version of some commands, i.e. to store and pop a
result in 32-bit integer format, use the instruction

	FISTP	<dword destination>

Also, Masm will automatically add FWAIT instructions to
8087 commands, i.e. FINIT will assemble into 9B DB E3.  To use
the "no-wait" form, use FNINIT, which assembles into DB E3.

	-- Herman