Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!pro-sol.cts.com!ruzun
From: ruzun@pro-sol.cts.com (Roger Uzun)
Newsgroups: comp.sys.apple
Subject: Re: benchmarking compilers vs. processors
Message-ID: <16859.apple.net@pro-sol>
Date: 17 Feb 90 00:52:54 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 17

In-Reply-To: message from dlyons@Apple.COM

>> Comment from David Lyons about benchmarks and C compilers.
You are quite right, the benchmarks in general test the system with
it compiler.  They bench the system and compiler together, and are unfair
to the system if the compiler is of low quality.  The fact that there are
a lot of high quality 680x0 compilers are a big plus for that architecture in
my opinion.  However note that lichty and eyes, in their 65816 book, indicate
that the 65816 is not as fast as a similar clocked 68000 for the sieve
benchmark in optimized assembler.  They further state that the sieve is a good
indication of cpu performance.  Note that the 68030 is 6 times faster than a
68000 at the same clock rate, if the 68000 is 0 wait states and the 68030 uses
a 1 wait state, burst mode enabled design.  All in all, a 65816 system could
probably not achieve 1/4th the speed, in hand optimized assembly benchmarks,
of a 68030 system clocked at the same speed.
 
-Roger