Xref: utzoo comp.sys.intel:497 comp.lang.c:12020 comp.arch:6130
Path: utzoo!utgpu!water!watmath!clyde!bellcore!rutgers!ucsd!ucsdhub!esosun!seismo!uunet!steinmetz!davidsen
From: davidsen@steinmetz.ge.com (William E. Davidsen Jr)
Newsgroups: comp.sys.intel,comp.lang.c,comp.arch
Subject: Re: Moving floating point values around
Message-ID: <11948@steinmetz.ge.com>
Date: 23 Aug 88 16:34:39 GMT
References: <4256@lynx.UUCP>
Reply-To: davidsen@crdos1.UUCP (bill davidsen)
Distribution: na
Organization: General Electric CRD, Schenectady, NY
Lines: 14

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 is a particular win for the 386, since it's one instruction.
However, in looking for that construct in code, I conclude that it
doesn't happen often enough to be a big win overall. I'd like to see the
compiler do it as a matter of generating good code, but I wouldn't
expect to see any big change in running time from it.
-- 
	bill davidsen		(wedu@ge-crd.arpa)
  {uunet | philabs | seismo}!steinmetz!crdos1!davidsen
"Stupidity, like virtue, is its own reward" -me