Re: optimizing compiler against average assembly programmer.

Ralph Boland <rboland@csi.uottawa.ca>
24 Jun 1997 23:38:24 -0400

          From comp.compilers

Related articles
optimizing compiler against iaverage assembly programmer. gclind01@starbase.spd.louisville.edu (1997-06-15)
Re: optimizing compiler against average assembly programmer. cef@geodseic.com (Charles Fiterman) (1997-06-19)
Re: optimizing compiler against average assembly programmer. tgl@netcom.com (1997-06-20)
Re: optimizing compiler against average assembly programmer. rboland@csi.uottawa.ca (Ralph Boland) (1997-06-24)
Re: optimizing compiler against average assembly programmer. dglaston@asc.corp.mot.com (Daniel Glastonbury) (1997-06-24)
Re: optimizing compiler against average assembly programmer. walter@bytecraft.com (Walter Banks) (1997-06-30)
Re: optimizing compiler against average assembly programmer. gclind01@starbase.spd.louisville.edu (1997-06-30)
Re: optimizing compiler against average assembly programmer. norman@kbss.bt.co.uk (Norman Hilton) (1997-06-30)
Re: optimizing compiler against average assembly programmer. debray@cs.arizona.edu (1997-06-30)
Re: optimizing compiler against average assembly programmer. cef@geodesic.com (Charles Fiterman) (1997-07-04)
[13 later articles]
| List of all articles for this month |
From: Ralph Boland <rboland@csi.uottawa.ca>
Newsgroups: comp.compilers,comp.lang.asm.x86
Date: 24 Jun 1997 23:38:24 -0400
Organization: Department of Computer Science, University of Ottawa
References: 97-06-071 97-06-074
Keywords: assembler, performance

Charles Fiterman wrote:
>
> The human should always win and here is why.
>
> First the human writes the whole thing in a high level language.
>
> Second he profiles it to find the hot spots where it spends
> its time.
>
> Third he has the compiler produce assembly for those small
> sections of code.
>
> Fourth he hand tunes them looking for tiny improvements over
> the machine generated code.
>
> The human wins because he can use the machine.




A valid point in theory but not overly practical. The
difficulty is that code needs to be modified. With each modification
of the high level code it must be recompiled by the machine (easy) and
reoptimized by the programmer. a painful task upon which to embark
after making a minor change.


The claim that we only need to to do the optimization on the
final version of code rarely occurs in practice. In the situation in
which it occurs though you would be right.


Ralph Boland
--


Post a followup to this message

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