Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!oliveb!pyramid!nsc!roger
From: roger@nsc.UUCP
Newsgroups: comp.arch,comp.sys.nsc.32k
Subject: Re: the NS32532
Message-ID: <4198@nsc.nsc.com>
Date: Sun, 12-Apr-87 22:30:25 EST
Article-I.D.: nsc.4198
Posted: Sun Apr 12 22:30:25 1987
Date-Received: Tue, 14-Apr-87 00:33:58 EST
References: <4190@nsc.nsc.com> <951@moscom.UUCP>
Organization: National Semiconductor, Sunnyvale
Lines: 19
Xref: utgpu comp.arch:852 comp.sys.nsc.32k:57

In article <951@moscom.UUCP>, jgp@moscom.UUCP (Jim Prescott) writes:

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

We provided a range of numbers, in an effort to allow people to
make up their own minds. Yes, it is true that the dhrystone benchmark
as well as others used today can be defeated by good compilers.  BUT
in the end application, which would you prefer to use.


Roger Thompson