Re: optimizing compiler against average assembly programmer.

Norman Hilton <norman@kbss.bt.co.uk>
30 Jun 1997 22:45:47 -0400

          From comp.compilers

Related articles
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)
Re: optimizing compiler against average assembly programmer. monnier+comp/compilers/news/@tequila.cs.yale.edu (Stefan Monnier) (1997-07-08)
[9 later articles]
| List of all articles for this month |

From: Norman Hilton <norman@kbss.bt.co.uk>
Newsgroups: comp.compilers,comp.lang.asm.x86
Date: 30 Jun 1997 22:45:47 -0400
Organization: Compilers Central
References: 97-06-074
Keywords: optimize, practice

Charles Fiterman wrote:
: 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.


Before step 3:


[S]he looks at the high level code for the hot spots and tries
to eliminate them using better algorithms and data structures.


An example of this is given in one of Jon Bentley's books,
and I can remember another one from a project I worked on
years ago (I won't bore you with details).


--


Norm (norman@kbss.bt.co.uk)
====
--


Post a followup to this message

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