Path: utzoo!attcan!uunet!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!sdd.hp.com!apollo!rehrauer
From: rehrauer@apollo.HP.COM (Steve Rehrauer)
Newsgroups: comp.sys.apollo
Subject: Re:  cc -g makes programs run faster?
Message-ID: <4ce31f7f.20b6d@apollo.HP.COM>
Date: 18 Sep 90 19:32:00 GMT
References: <9009181421.AA22513@richter.mit.edu>
Sender: root@apollo.HP.COM
Reply-To: rehrauer@apollo.HP.COM (Steve Rehrauer)
Organization: Hewlett-Packard Apollo Division - Chelmsford, MA
Lines: 15

In article <9009181421.AA22513@richter.mit.edu> krowitz@RICHTER.MIT.EDU (David Krowitz) writes:
>A factor of three speed increase (for floating point code) is usually
>what I get from going from a " cpu any" (the default) to a "cpu 3000"
>(which turns on the use of inline floating point code and the 68020
>specific addressing modes). It's mere speculation, but maybe your
>"cpu,3000" isn't getting through to the compiler in the first case?

To verify that this is or isn't the case, you could try specifying
-## or -### to /bin/cc.  The former causes the expanded command-line
that is actually passed to /com/cc to be echoed before compilation
proceeds.  The latter just echoes the command-line, without proceeding
with compilation.
--
   >>"Aaiiyeeee!  Death from above!"<<     | (Steve) rehrauer@apollo.hp.com
"Spontaneous human combustion - what luck!"| Apollo Computer (Hewlett-Packard)