Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!haven!rutgers!att!pegasus!psrc
From: psrc@pegasus.ATT.COM (Paul S. R. Chisholm)
Newsgroups: comp.sys.att,u3b.misc
Subject: Re: Compiling for non-MAU systems
Summary: -Kc == compatibility mode
Keywords: 3B2
Message-ID: <2549@pegasus.ATT.COM>
Date: 26 Jan 89 23:37:25 GMT
References: <1670@lamc.UUCP>
Organization: AT&T Bell Laboratories
Lines: 23

<"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.