Xref: utzoo comp.sys.intel:498 comp.lang.c:12024 comp.arch:6132
Path: utzoo!attcan!uunet!husc6!uwvax!oddjob!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.sys.intel,comp.lang.c,comp.arch
Subject: Re: Moving floating point values around
Message-ID: <13148@mimsy.UUCP>
Date: 23 Aug 88 13:05:44 GMT
References: <4256@lynx.UUCP>
Distribution: na
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 12

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?

Probably safe: the 4.3BSD C compiler (actually, peephole optimiser)
can be told to change movf and movd instructions to movl and movq
(`/lib/c2 -f').  This is used by the f77 compiler; it improves some
benchmarks rather surprisingly.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris