|Public domain Pcode spec/interpreter ? firstname.lastname@example.org (1994-09-11)|
|Public domain Pcode spec/interpreter PAUL@tdr.com (Paul Robinson) (1994-09-17)|
|Re: Public domain Pcode spec/interpreter email@example.com (1994-09-17)|
|Re: Public domain Pcode spec/interpreter firstname.lastname@example.org (1994-09-18)|
|Re: Public domain Pcode spec/interpreter email@example.com (1994-09-20)|
|Re: Public domain Pcode spec/interpreter firstname.lastname@example.org.Uni-Osnabrueck.DE (1994-09-21)|
|From:||email@example.com (David Keppel)|
|Organization:||Computer Science & Engineering, U. of Washington, Seattle|
|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
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
Search the comp.compilers archives again.