Re: optimizing compiler against average assembly programmer.

Charles Fiterman <cef@geodseic.com>
19 Jun 1997 00:03:55 -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)
[15 later articles]
| List of all articles for this month |
From: Charles Fiterman <cef@geodseic.com>
Newsgroups: comp.compilers,comp.lang.asm.x86
Date: 19 Jun 1997 00:03:55 -0400
Organization: Geodesic Systems
References: 97-06-071
Keywords: optimize, assembler

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.
--

Post a followup to this message

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