Newsgroups: comp.sys.amiga.tech
Path: utzoo!utgpu!watserv1!maytag!maytag!himacdon
From: himacdon@maytag.uwaterloo.ca (Hamish Macdonald)
Subject: Re: What's Wrong with ARP!!!!
In-Reply-To: cedman@golem.ps.uci.edu's message of 15 Nov 90 03:32:02 GMT
Message-ID: <1990Nov15.160222.23856@maytag.waterloo.edu>
Sender: daemon@maytag.waterloo.edu (Admin)
Organization: University of Waterloo, Waterloo, Ontario
References: <114.273F7E66@myamiga.UUCP> <1990Nov14.034507.19784@hoss.unl.edu>
	<7039@sugar.hackercorp.com> <90318.162021DXB132@psuvm.psu.edu>
	<CEDMAN.90Nov14193209@lynx.ps.uci.edu>
Date: Thu, 15 Nov 90 16:02:22 GMT
Lines: 25

>>>>> In article <CEDMAN.90Nov14193209@lynx.ps.uci.edu>,
>>>>> cedman@golem.ps.uci.edu (Carl Edman) writes:

Carl> And now using assembler is a "big no-no" ? What is the world coming to ?

Today's CPUs are becoming more and more complicated, making it more
difficult to write correct assembler code (especially RISC CPUs, or a
multiprocessor environment, or a combination of the two).

Of course, the compiler writers have similar problems in ensuring that
the code their compilers generate is correct, but at least that is
done in only one place, not in every program you write (I know, I
know, it is difficult if not impossible to _prove_ that a compiler
generates correct code in all instances...)

In any case, compilation by a C compiler followed either by
hand-optimization of the assembly code generated (if any), or by going
back to the code and re-coding inefficient-generated or most-used
sections should get you both the fast-development time and the program
performance you require.

Hamish.
--
--------------------------------------------------------------------
himacdon@maytag.uwaterloo.ca                 watmath!maytag!himacdon
