Related articles |
---|
[9 earlier articles] |
Re: Effectiveness of compilers today roth@helena.cs.rice.edu (1993-02-18) |
Re: Effectiveness of compilers today pardo@cs.washington.edu (1993-02-19) |
Re: Effectiveness of compilers today kjb@cgl.citri.edu.au (1993-02-19) |
Re: Effectiveness of compilers today kanze@us-es.sel.de (1993-02-20) |
Re: Effectiveness of compilers today tchannon@black.demon.co.uk (1993-02-19) |
Re: Effectiveness of compilers today korz@cs.columbia.edu (1993-02-22) |
Re: Effectiveness of compilers today henry@zoo.toronto.edu (1993-02-24) |
Re: Effectiveness of compilers today lindsay+@cs.cmu.edu (1993-03-02) |
Re: Effectiveness of compilers today preston@dawn.cs.rice.edu (1993-03-03) |
Newsgroups: | comp.compilers |
From: | henry@zoo.toronto.edu (Henry Spencer) |
Keywords: | optimize, assembler |
Organization: | U of Toronto Zoology |
References: | 93-02-082 93-02-116 |
Date: | Wed, 24 Feb 1993 21:59:18 GMT |
kanze@us-es.sel.de (James Kanze) writes:
>... This code sequence is a well known trick regularly
>used by 8086 assembly programmers 10 years back. So it should hardly
>require a super-optimizer to find it...
That one code sequence is not the only justification for the
super-optimizer! Sure, a machine that gets programmed a lot in assembler
builds up a body of folklore over the years about cute ways of doing
things. Sometimes, some of it even gets written down. The point of the
super-optimizer is being able to discover these things systematically
without having to wait five years for the experience to build up
(especially since assembler programming is getting less common all the
time).
--
Henry Spencer @ U of Toronto Zoology | henry@zoo.toronto.edu utzoo!henry
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.