Related articles |
---|
Architecture description languages for compilers? eigenstr@cs.rose-hulman.edu (1993-01-25) |
Architecture description languages for compilers? tac@eos.ncsu.edu (1993-01-26) |
Re: Architecture description languages for compilers? brent@eng.uiowa.edu (1993-01-27) |
Re: Architecture description languages for compilers? arh@cix.compulink.co.uk (Andrew Henson) (1993-01-27) |
Re: Architecture description languages for compilers? pardo@cs.washington.edu (1993-01-28) |
Re: Architecture description languages for compilers? zstern@adobe.com (1993-01-28) |
Re: Architecture description languages for compilers? wjw@eb.ele.tue.nl (1993-02-01) |
Newsgroups: | comp.compilers |
From: | Andrew Henson <arh@cix.compulink.co.uk> |
Organization: | Compilers Central |
Date: | Wed, 27 Jan 1993 17:09:00 GMT |
References: | 93-01-180 |
Keywords: | architecture, bibliography |
eigenstr@cs.rose-hulman.edu (Todd R. Eigenschink) writes:
> I'm planning on doing some research in optimization and code generation
> next quarter. One of the topics I'm interested in is machine
> descriptions--some vanilla way to describe the architecture of a machine
> for purposes of code generation. (Numbers of registers, addressing modes,
> etc.)
Try:
Davidson J W & Fraser C W "Register allocation and Exhaustive
Peephole Optimization" Software-Practice and Experience Vol 14(9)
857-865 (September 1984)
Davidson J W & Fraser C W "Code selection through Object Code
Optimization" ACM Trans Prog Lang Vol6(4) (October 84) 505-526
Davidson J W & Whalley D B "Quick Compilers Using Peephole
Optimisation" Software-Practice and Experience Vol19(1) 79-97
(January 89)
The basic idea is to generate code very crudely and optimise very well it
using an exhaustive search of actual instructions. Instructions are
stored using a Register Transfer Language.
The exhaustive search is expensive, so commonly used ones are cached.
--
Andy Henson; voice: +44.923.825275; voicemail: +44.426.910223
arh@cix.compulink.co.uk; Cix is a mail service: I'm independent.
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.