Related articles |
---|
Two questions about compiler design blitz@bad-logic.com (2004-02-01) |
Re: Two questions about compiler design david.waller1@blueyonder.co.uk (david.waller) (2004-02-04) |
Re: Two questions about compiler design david.waller1@blueyonder.co.uk (david.waller) (2004-02-04) |
Re: Two questions about compiler design Jeffrey.Kenton@comcast.net (Jeff Kenton) (2004-02-04) |
Re: Two questions about compiler design isaac@latveria.castledoom.org (Isaac) (2004-02-08) |
Re: Two questions about compiler design peteg@cse.unsw.EDU.AU (Peter Gammie) (2004-02-12) |
Re: Two questions about compiler design j.troeger@qut.edu.au (Jens Troeger) (2004-02-12) |
Re: Two questions about compiler design samiam@moorecad.com (Scott Moore) (2004-02-12) |
[3 later articles] |
From: | "david.waller" <david.waller1@blueyonder.co.uk> |
Newsgroups: | comp.compilers |
Date: | 4 Feb 2004 21:48:23 -0500 |
Organization: | blueyonder (post doesn't reflect views of blueyonder) |
References: | 04-02-030 |
Keywords: | design |
Posted-Date: | 04 Feb 2004 21:48:23 EST |
You could use the following as "intermediate code"
Java Virtual Machine code
or the Intermediate code from .NET. Both have plenty of documentation as
to the standard and would have the advantage that you don't need to write
the interpreter.
Alternatively there is Pcode, a very simple stack based system (compared to
the above two). There are references
available on the Internet for Pcode and an interpreter is easy to write for
Pcode.
"Blitz" <blitz@bad-logic.com> wrote in message
> I've basically read most of the dragon book, and according to that
> book you should generate intermediate code then divide it into basic
> blocks+flow chart then build a DAG for each basic block to do code
> motion etc etc. Now, all this seems great to me. But the book i have
> is from -79 and i'm wondering if this is pretty much how it's done
> now days as well? ...
Return to the
comp.compilers page.
Search the
comp.compilers archives again.