Re: optimizing compiler against iaverage assembly programmer.

George C. Lindauer wrote:


> 2) in the real world we have two reasons for the average programmer's
> dilemma: a) skill and b) constraints of management that often
> emphasize fast turnaround over good engineering? A good optimizing


Well, frankly, fast turnaround and good engineering *both* tend to
result in slower code.


> where compilers fit in the scheme of things? Are good optimizing
> compilers really all they are cracked up to be? Or is it simply true
> that academic types like to think their work important and business
> types accept it because they can turn out more inefficient code,
> faster, and still have things run just barely well enough to satisfy
> their customers? (with of course the help of hardware types who make


Well, I've never seen a compiler that was better than a typical
assembly coder, but the truth is that the costs of coding in assembly
don't pay for the benefits. Hand-coded assembly tends to be a little
faster, but not enough to make it worth the effort. In the end, barely
fast enough to satisfy customers is exactly where you should aim, as a
professional. Anything more is risking bugs and extra development
time, for no significant benefit.
--
Got Atari stuff to get rid of? Virtual Boy? Looking for M:TG cards, L5R,
ShadowFist, Guardians? Want more Atari or Sega stuff? Mail me, or visit:
http://www.angelfire.com/tn/squirrels
--

Return to the comp.compilers page.
Search the comp.compilers archives again.