Related articles |
---|
Public domain Pcode spec/interpreter ? timc@intel.com (1994-09-11) |
Public domain Pcode spec/interpreter PAUL@tdr.com (Paul Robinson) (1994-09-17) |
Re: Public domain Pcode spec/interpreter pardo@cs.washington.edu (1994-09-17) |
Re: Public domain Pcode spec/interpreter ellard@bbn.com (1994-09-18) |
Re: Public domain Pcode spec/interpreter markl@netcom.com (1994-09-20) |
Re: Public domain Pcode spec/interpreter bfaust@saratoga.physik.Uni-Osnabrueck.DE (1994-09-21) |
Newsgroups: | comp.compilers |
From: | pardo@cs.washington.edu (David Keppel) |
Keywords: | code |
Organization: | Computer Science & Engineering, U. of Washington, Seattle |
References: | 94-09-033 94-09-070 |
Date: | Sat, 17 Sep 1994 21:40:25 GMT |
John Levine writes:
>[There have been lots of systems that use p-code to permit highly portable
>binaries. ...]
As a historical footnote, I recall my cousin (an old-time hacker) said
that a company in the 60's wrote most of their compilers in a virtual
machine code. Retargeting meant writing a new back-end, a new
interpreter, and some key inner loops, but the basic task was
simplified over a machine language port. Speed was OK because the
v-code primitives were tuned to common compiler tasks.
If anybody wants details, let me know and I'll ask for 'em.
;-D on ( History hysteria ) Pardo
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.