Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site hadron.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!mhuxn!mhuxr!ulysses!allegra!mit-eddie!genrad!panda!talcott!harvard!seismo!trwatf!rlgvax!prcrs!hadron!jsdy
From: jsdy@hadron.UUCP (Joseph S. D. Yao)
Newsgroups: net.micro.att
Subject: Re: What's wrong with this program (3b2)?
Message-ID: <199@hadron.UUCP>
Date: Sat, 22-Jun-85 07:43:37 EDT
Article-I.D.: hadron.199
Posted: Sat Jun 22 07:43:37 1985
Date-Received: Mon, 24-Jun-85 06:45:07 EDT
References: <104@gwsd.UUCP> <476@gitpyr.UUCP> <339@cuae2.UUCP>
Reply-To: jsdy@hadron.UUCP (Joseph S. D. Yao)
Organization: Hadron, Inc., Fairfax, VA
Lines: 16
Keywords: cc, -f, 3B2, floating point
Summary: '-f' should be automatic!

In article <339@cuae2.UUCP> heiby@cuae2.UUCP (Ron Heiby) writes:
>In article <476@gitpyr.UUCP> robert@gitpyr.UUCP (Robert Viduya) writes:
>>There's an undocumented flag for the cc command which enables generation
>>of software floating point support.
>I think it should be pointed out that the flag is documented ...
>   -f   Link the object program with the floating-point
>        interpreter for systems without hardware floating-point.

I think a major point is, if the 3B2  n e e d s  the '-f' flag, it
should automagically be included at compile time.  We did this for
PDP-11's without floating point:  there was a compile-time option
(when compiling the C compiler!) to determine whether -f was a
compiler option or requirement.  (We == the UNIX community;
reference == V5/V6 ff -- pre-COFF days.)

	Joe Yao		hadron!jsdy@seismo.{ARPA,UUCP}