Related articles |
---|
General byte-codes reference mak@imakhno.freeserve.co.uk (Makhno) (2000-12-07) |
Re: General byte-codes reference s337240@student.uq.edu.au (Trent Waddington) (2000-12-08) |
Re: General byte-codes reference evilzr@yahoo.com (Daniel Dunbar) (2000-12-08) |
Re: General byte-codes reference anton@mips.complang.tuwien.ac.at (2000-12-11) |
Re: General byte-codes reference midkiff@watson.ibm.com (2000-12-11) |
Re: General byte-codes reference Norman_member@newsguy.com (Norman Culver) (2000-12-18) |
Re: General byte-codes reference brangdon@cix.compulink.co.uk (2000-12-18) |
Re: General byte-codes reference patc@acm.org (Pat Caudill) (2000-12-18) |
Re: General byte-codes reference sjmeyer@www.tdl.com (2000-12-20) |
[2 later articles] |
From: | Daniel Dunbar <evilzr@yahoo.com> |
Newsgroups: | comp.compilers |
Date: | 8 Dec 2000 22:22:44 -0500 |
Organization: | Virginia Tech, Blacksburg, Virginia, USA |
References: | 00-12-030 |
Keywords: | interpreter |
Posted-Date: | 08 Dec 2000 22:22:44 EST |
You may find the following paper interesting, it details the design of
the virtual machine for the Inferno operating platform, and discusses
some of the tradeoffs that were made, mostly with regard to memory
bandwidth and on-the-fly compilation support.
http://www.vitanuova.com/inferno/papers/hotchips.html
--
daniel dunbar
evilzr@yahoo.com
Return to the
comp.compilers page.
Search the
comp.compilers archives again.