🚀 go-pugleaf

In article <4jq1dc$a1g@solutions.solon.com>,
richard mross <uar@southwind.net> wrote:
>compile both cases with the "generate assembly output file"  option
>and compare the assemply output, then count the cpu cycles for each of
>the instructions used on each of the outputs

Someone should note that this approach really only works for extremely
simple systems (no virtual memory, no cache, no superscalar, etc.).
These performance enhancers also add a lot of variability to how
long a given instruction takes.  Someone who is good enough to be
able to predict cache hit rates (and how they will affect the
performance of the code) from a static analysis of the assembly
output probably wouldn't be posting here asking which approach
was more efficient.  For most people, actual measurement of the
run time on the intended hardware is a better way to go.
-- 
Dave Wallace		(wallace@netcom.com)