|Interpretable intermediate code design? email@example.com (Joachim Durchholz) (1998-02-12)|
|Re: Interpretable intermediate code design? firstname.lastname@example.org (David Chase) (1998-02-14)|
|Re: Interpretable intermediate code design? email@example.com (Robert Trevellyan) (1998-02-14)|
|Re: Interpretable intermediate code design? firstname.lastname@example.org (Alexander Kjeldaas) (1998-02-20)|
|From:||Alexander Kjeldaas <email@example.com>|
|Date:||20 Feb 1998 17:57:50 -0500|
|Organization:||Guardian Networks AS|
[Joachim Durchholz <firstname.lastname@example.org>]
| I'm in need for an intermediate code format that's also usable as VM
| code. References to relevant design principles preferred, though
| existing designs are appreciated, too. I.e. I know the JVM format
| (roughly), but I don't know wether it's good or bad, and even if I
| knew I wouldn't know why and I wouldn't be able to improve on it.
The following papers from The SIGPLAN Workshop on Intermediate
Representations (IR '95) could be interesting. The first basically
describes the JavaVM, while the other describes a competing
intermediate code developed at sun that is quite fast.
Oak Intermediate Bytecodes by James Gosling (Sun Microsystems
Clarity Mcode: A Retargetable Intermediate Representation for
Compilation by Brian T. Lewis (Sun Microsystms Laboratories).
IR '95 is available for free [but not online] as a technical report
from Microsoft Research.
Alexander Kjeldaas, Guardian Networks AS, Trondheim, Norway
Return to the
Search the comp.compilers archives again.