Re: optimizing compiler against average assembly programmer.

gclind01@starbase.spd.louisville.edu (George C. Lindauer)
30 Jun 1997 00:11:00 -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)
Re: optimizing compiler against average assembly programmer. vkarvone@raita.oulu.fi (1997-07-04)
Re: optimizing compiler against average assembly programmer. rhyde@cs.ucr.edu (1997-07-04)
Re: optimizing compiler against average assembly programmer. WStreett@shell.monmouth.com (1997-07-08)
[12 later articles]
| List of all articles for this month |

From: gclind01@starbase.spd.louisville.edu (George C. Lindauer)
Newsgroups: comp.compilers,comp.lang.asm.x86
Followup-To: comp.compilers,comp.lang.asm.x86
Date: 30 Jun 1997 00:11:00 -0400
Organization: University of Louisville
References: 97-06-071 97-06-082
Keywords: performance

: system, and gives reasons to think that a factor-of-ten speedup at
: *each* design level might be achievable compared to what was then
: state of the art. Multiply it out, and you get a speedup factor of
: one million. *That* is the real reason why humans should not be
: spending their time doing assembly programming, except perhaps on
: critical hotspot routines identified by profiling. Don't try to
: replace a compiler; use it to multiply your own abilities.


On a philosophical note that will probably get stripped by the moderator,
WHY is the speedup factor important? WHY can't I tread along like a turtle
if I want, instead being forced to race along at 300 MPH?


David
[There's been plenty of work on program pessimization. I can cite one
program that after pessimization improved a little program that ran at
a wasteful 15% CPU utilization up to a highly cost-efficient 98%
utilization. Similar improvements in RAM usage have been observed. -John]


--


Post a followup to this message

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