Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!husc6!seismo!rochester!ritcv!moscom!jgp
From: jgp@moscom.UUCP
Newsgroups: comp.arch,comp.sys.nsc.32k
Subject: Re: the NS32532
Message-ID: <951@moscom.UUCP>
Date: Sat, 11-Apr-87 16:38:54 EST
Article-I.D.: moscom.951
Posted: Sat Apr 11 16:38:54 1987
Date-Received: Sun, 12-Apr-87 19:36:29 EST
References: <4190@nsc.nsc.com>
Reply-To: jgp@moscom.UUCP (Jim Prescott)
Organization: MOSCOM Corp, E Rochester, NY, USA
Lines: 28
Xref: utgpu comp.arch:840 comp.sys.nsc.32k:51

In article <4190@nsc.nsc.com> roger@nsc.nsc.com (Roger Thompson) writes:
>	32332 @ 15 MHZ version 1.0 optimized ............ 3943.5
>	32332 @ 15 MHZ version 1.1 optimized ............ 3183.0
>	32332 @ 15 MHZ version 1.1 no global opt......... 2724.0
>
>	32532 @ 30 MHZ version 1.0 optimized ............ 19800
>	32532 @ 30 MHZ version 1.1 optimized ............ 16600
>	32532 @ 30 MHZ version 1.1 no global opt ........ 14100
>
>	Yes we have a new set of compilers in the works that among
>	other things supports global optimizations.
Unfortunately the Dhrystone benchmark does not support global
optimizations; it says so right in the instructions.  A good
global optimizer would reduce dhrystone to a few arithmetic
instructions, 2 calls to times() and 1 to write().  As current
global optimizers get better they will aproach this ideal by
eliminating more and more code that does nothing in the benchmark
but accomplishes real work in the code the benchmark is supposed
to represent.

The above numbers represent a dhrystone rating of about 14000, not
the 18000 previously quoted.

Of course, the above applies to everyone, I don't mean to single
out nsc.  If your going to publish a dhrystone number (or any
benhmark for that matter) keep the global optimizers away from it.
-- 
Jim Prescott	rochester!moscom!jgp