Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!purdue!haven!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.sys.apple
Subject: Re: benchmarking compilers vs. processors
Message-ID: <12148@smoke.BRL.MIL>
Date: 14 Feb 90 22:55:11 GMT
References: <16747.apple.net@pro-sol> <38645@apple.Apple.COM>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 14

In article <38645@apple.Apple.COM> dlyons@Apple.COM (David A. Lyons) writes:
>I've never seen a 65816 C compiler produce impressive object code--
>benchmarking a compiler isn't the same thing as benchmarking the
>processor.

If one is going to be using the compiler, then it had better be included
in the performance measurement!

ORCA/C doesn't seem to do too badly when full optimization is enabled.

I long ago learned not to code in assembly language unless it was forced
by the circumstances (e.g. in writing some of the run-time support for a
compiler).  My time is too valuable to waste like that on a one-machine
project.