Xref: utzoo comp.sys.intel:501 comp.lang.c:12041 comp.arch:6138
Path: utzoo!utgpu!water!watmath!clyde!bellcore!tness7!ninja!dalsqnt!rpp386!jfh
From: jfh@rpp386.UUCP (The Beach Bum)
Newsgroups: comp.sys.intel,comp.lang.c,comp.arch
Subject: Re: Moving floating point values around
Summary: as long as you aren't moving for side effects, do it
Message-ID: <5733@rpp386.UUCP>
Date: 24 Aug 88 00:53:16 GMT
References: <4256@lynx.UUCP>
Reply-To: jfh@rpp386.UUCP (The Beach Bum)
Distribution: na
Organization: HASA, "S" Division
Lines: 21

In article <4256@lynx.UUCP> m5@lynx.UUCP (Mike McNally) writes:
>How naughty would it be for a compiler for the 386/387 (or 286/287 for that
>matter) to move floating-point values with 386 MOV instructions instead
>of FLD and FSTP?

this shouldn't be a bother.  you should be able to use the doubleword
load and store instructions (or the block byte moves if you want) to
move floats and doubles.

the only place you have to watch out for is

	if (f1 = f2)
		...

or some other conditional context.  you have to use the floating point
moves or a floating point test to properly set the condition codes.
-- 
John F. Haugh II (jfh@rpp386.UUCP)                           HASA, "S" Division

    "If the code and the comments disagree, then both are probably wrong."
                -- Norm Schryer