Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!eecae!netnews.upenn.edu!rutgers!njin!princeton!njsmu!mccc!pjh
From: pjh@mccc.UUCP (Pete Holsberg)
Newsgroups: comp.sys.att,u3b.misc
Subject: Re: Compiling for non-MAU systems
Keywords: 3B2
Message-ID: <590@mccc.UUCP>
Date: 29 Jan 89 04:02:22 GMT
References: <1670@lamc.UUCP> <2549@pegasus.ATT.COM>
Reply-To: pjh@mccc.UUCP (Pete Holsberg)
Organization: The College On The Other Side of U. S. Route 1
Lines: 37

In article <2549@pegasus.ATT.COM> psrc@pegasus.ATT.COM (Paul S. R. Chisholm) writes:
=<"He seemed like such a nice man . . . and then he turned out to be a writer!">
=
=Whoever compiles the Info-3B2 Digest passed along a question about
=building a product that will run on a 3B2 without a Math Accelerator
=Unit (MAU).
=
=The -K flag (described in some version of TFM, cc(1)) controls such
=options.  As described in the CPLU 4.2 Release Notes (now, aren't you
=embarrassed that that wasn't the first place you looked?-), there are
=three possibilities.  -Kmau (probably the default) generates code for
=an MAU.  -Kfpe ("floating point emulation") compiles your program to
=run on a 32100- or 32200-based system (that is, anything but a
=3B2/300).  -Kc ("compatibility") produces .o and a.out files that will
=run on any 3B2 ever made.
=
=While your reading the release notes, you should notice that -Ksd (or
=is it -Ksp? anyway, the default) tells the optimizer to increase your
=program's speed, while -Ksz will improve (decrease) your software's
=size.
=

=Paul S. R. Chisholm, psrc@pegasus.att.com (formerly psc@lznv.att.com)
=AT&T Bell Laboratories, att!pegasus!psrc, AT&T Mail !psrchisholm
=I'm not speaking for the company, I'm just speaking my mind.


That's fine if you have cc.  My system has fpcc only.  Now aren't you
sorry you were snide?

Pete

-- 
Pete Holsberg                   UUCP: {...!rutgers!}princeton!mccc!pjh
Mercer College			CompuServe: 70240,334
1200 Old Trenton Road           GEnie: PJHOLSBERG
Trenton, NJ 08690               Voice: 1-609-586-4800