|P-Code and virtual machines email@example.com (1994-03-23)|
|Re: P-Code and virtual machines firstname.lastname@example.org (1994-03-25)|
|Re: P-Code and virtual machines email@example.com (1994-03-28)|
|Re: P-Code and virtual machines firstname.lastname@example.org) (1994-04-05)|
|Re: P-Code and virtual machines email@example.com (1994-04-08)|
|From:||firstname.lastname@example.org (David Keppel)|
|Organization:||Computer Science & Engineering, U. of Washington, Seattle|
|Date:||Fri, 25 Mar 1994 02:41:08 GMT|
email@example.com (Gerard Henri Rene Milmeister) writes:
>[Books or papers on the instruction set of an interpreter for a
> procedural language? I have experience with stack machines and they
> seem inappropriate for e.g., C.]
I can't say how appropriate they are, but several older machines (e.g., HP
and Tandem) used *hardware* stack machines and ran e.g., FORTRAN. Stack
machines have the advantage that the code is compact, easy to decode and
easy to convert to threaded code (for fast decode) and can be implemented
with similar efficiency across a fair range of machines.
Virtual machines that have a modest number of (virtual) registers may work
well on host machines with, say, double the number of hardware registers
but may perform worse on machines with a limited number of registers.
An alternative is to (dynamically) compile the v-code to n-code or a
machine-specific v-code in order to improve register allocation.
;-D on ( Virtual vegetables ) Pardo
Return to the
Search the comp.compilers archives again.