Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!ucbcad!ucbvax!decvax!tektronix!tekcrl!terryl
From: terryl@tekcrl.UUCP
Newsgroups: comp.arch,comp.sys.nsc.32k
Subject: Re: Re: the NS32532
Message-ID: <1582@tekcrl.TEK.COM>
Date: Tue, 14-Apr-87 18:03:50 EST
Article-I.D.: tekcrl.1582
Posted: Tue Apr 14 18:03:50 1987
Date-Received: Thu, 16-Apr-87 01:14:19 EST
References: <4190@nsc.nsc.com> <951@moscom.UUCP> <2577@intelca.UUCP> <219@homxb.UUCP>
Reply-To: terryl@tekcrl.tek.com
Organization: Tektronix, Inc., Beaverton, OR.
Lines: 22
Xref: utgpu comp.arch:874 comp.sys.nsc.32k:67

In article <219@homxb.UUCP> gemini@homxb.UUCP (Rick Richardson) writes:
+In article <2577@intelca.UUCP>, clif@intelca.UUCP (Clif Purkiser) writes:
+> While, I agree that using a global optimizing compiler is not exactly
+> kosher for the dhrystone benchmark it sometimes neccessary.  For 
+> instance: the GreenHills C compiler is a globally optimizing compiler
+> which generates good Dhrystone numbers for many architectures including
+> the 80386 and 68020.	 Unfortunately, I can not find a compiler
+> switch to turn off the global optimizer.
+
+Is this true?  I have many results using the GreenHills compiler which
+are not marked as having a global optimizer turned on.  Are you sure
+there's no switch to turn it off?  

     Well, yes and no. Since Greenhills supports symbolic debugging (at
least for a 68020 system), with the "-g" option, Mr. Richardson is right.
BUT, baring that, the only option I could find to "turn off" optimization
is the -X9 option, which is to disable the local(peephole) optimizer. So
Mr. Purkiser is right.

     Actually, there are a couple of more options to disable optimization,
like not moving frequently used procedure and data addresses into registers,
but I doubt that would cause much of a discrepancy.