Related articles |
---|
code generator generators? mike@vlsivie.tuwien.ac.at (1991-09-05) |
Re: code generator generators? pardo@gar.cs.washington.edu (1991-09-06) |
Re: code generator generators? horst@techfak.uni-bielefeld.de (1991-09-09) |
Re: code generator generators? bill@hcx2.ssd.csd.harris.com (1991-09-09) |
Re: code generator generators? shuksan!scott@bcstec.ca.boeing.com (1991-09-09) |
Re: code generator generators? clifton_r@zon.verifone.com (Clifton Royston HNL (808)625-3234) (1991-09-12) |
Re: code generator generators? jourdan@minos.inria.fr (1991-09-16) |
Re: code generator generators? robichau@freedom.msfc.nasa.gov (1991-09-17) |
Newsgroups: | comp.compilers |
From: | jourdan@minos.inria.fr (Martin Jourdan) |
Keywords: | code, bibliography, design |
Organization: | INRIA, Rocquencourt, France |
References: | 91-09-012 91-09-014 91-09-021 |
Date: | 16 Sep 91 12:54:16 GMT |
In article 91-09-021, horst@techfak.uni-bielefeld.de (horst Hogenkamp) writes:
> BEG (back end generator):
> =========================
> This is probably one of the best:
>
> Helmut Emmelmann: BEG - a Back End Generator - Users Manual
> GMD Forschungsstelle an der Universitaet Karlsruhe
> Vincenz-Priessnitz-Str. 1
> W7500 Karlsruhe
> GERMANY
A much easier to find reference is:
H. Emmelmann, F.-W Schro"er & R. Landwehr:
BEG - A Generator for Efficient Back Ends
SIGPLAN '89 PLDI conf., Portland, Or.
SIGPLAN Notices 24, 7 (July 1989), pp. 227-237
BEG is a tool good enough for production use but, as many of its competitors,
it concentrates on instruction scheduling and is weak on other issues
(register allocation, instruction scheduling, peephole optimization, etc.).
At INRIA we are working on Pagode, with the explicit aim of producing
subprograms performing all of the above tasks from a single, easy-to-write
machine description. However we're still far from our goal... For more
information, get in touch with Monique Mazaud (Monique.Mazaud@inria.fr).
Martin Jourdan <Martin.Jourdan@inria.fr> INRIA, Rocquencourt, France.
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.