Computer Old Farts Forum
 help / color / mirror / Atom feed
* Re: [COFF] [TUHS] Compilation "vs" byte-code interpretation, was Re: Looking back to 1981 - what pascal was popular on what unix?
       [not found]             ` <CABH=_VS7G1XqO03NRkvSXEr8EiHWWP_sGyRnVNxV9wt3G9W_EQ@mail.gmail.com>
@ 2022-02-02  4:53               ` Adam Thornton
  0 siblings, 0 replies; 2+ messages in thread
From: Adam Thornton @ 2022-02-02  4:53 UTC (permalink / raw)
  To: Computer Old Farts Followers


[-- Attachment #1.1: Type: text/plain, Size: 655 bytes --]

On Mon, Jan 31, 2022 at 10:17 AM Paul Winalski <paul.winalski@gmail.com>
wrote:

> On 1/30/22, Steve Nickolas <usotsuki@buric.co> wrote:
> > And I think I've heard the Infocom compilers' bytecode called "Z-code" (I
> > use this term too).
> That is correct.  The Infocom games ran on an interpreter for an
> abstract machine called the Z-machine.  Z-code is the Z-machine's
> instruction set.  There is a freeware implementation out there called
> Frotz.
>
>
There's a reasonably functional Frotz implementation for TOPS-20, as it
happens.  The ZIP interpreter was easier to port to 2.11BSD on the PDP-11.

https://github.com/athornton/tops20-frotz

Adam

[-- Attachment #1.2: Type: text/html, Size: 1216 bytes --]

[-- Attachment #2: Type: text/plain, Size: 141 bytes --]

_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [COFF] Compilation "vs" byte-code interpretation, was Re: Looking back to 1981 - what pascal was popular on what unix?
       [not found]     ` <CAGGBd_r24ODfR9oX_sMHkDWOotz9Bhup=CgDEgC=NNq9BFuNcg@mail.gmail.com>
       [not found]       ` <CAEoi9W6qovywr7KrJtXx5s-MKhC19pj5-VqQ0_1zoT-MaWRdSA@mail.gmail.com>
@ 2022-02-02  8:46       ` Peter Jeremy via COFF
  1 sibling, 0 replies; 2+ messages in thread
From: Peter Jeremy via COFF @ 2022-02-02  8:46 UTC (permalink / raw)
  To: Dan Stromberg; +Cc: Computer Old Farts Followers


[-- Attachment #1.1: Type: text/plain, Size: 1807 bytes --]

=> COFF

On 2022-Jan-30 10:07:15 -0800, Dan Stromberg <drsalists@gmail.com> wrote:
>On Sun, Jan 30, 2022 at 8:58 AM David Barto <david@kdbarto.org> wrote:
>
>> Yes, the UCSD P-code interpreter was ported to 4.1 BSD on the VAX and it
>> ran natively there. I used it on sdcsvax in my senior year (1980).
>
>This reminds me of a question I've had percolating in the back of my mind.
>
>Was USCD Pascal "compiled" or "interpreted" or both?
>
>And is Java?  They both have a byte code interpreter.

A bit late to the party but my 2¢:

I think it's fairly clear that both UCSD Pascal and Java are compiled
- to binary machine code for a p-code machine or JVM respectively.
That's no different to compiling (eg) C to PDP-11 or amd64 binary
machine code.

As for how the machine code is executed:
* p-code was typically interpreted but (as mentioned elsewhere) there
  were a number of hardware implementions.
* Java bytecode is often executed using a mixture of interpretation
  and (JIT) compilation to the host's machine code.  Again there are
  a number of hardware implementations.

And looking the other way, all (AFAIK) PDP-11's were microcoded,
therefore you could equally well say that PDP-11 machine code is being
interpreted by the microcode on a "real" PDP-11.  And, nowadays,
PDP-11 machine code is probably more commonly interpreted using
something like simh than being run on a hardware PDP-11.

Typical amd64 implementations are murkier - with machine code being
further converted ("compiled"?) into a variable number of micro-ops
that have their own caches and are then executed on the actual CPU.  
(And, going back in time, the Transmeta Crusoe explicity did JIT
conversion from iA32 machine code to its own proprietary machine code).

-- 
Peter Jeremy

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 963 bytes --]

[-- Attachment #2: Type: text/plain, Size: 141 bytes --]

_______________________________________________
COFF mailing list
COFF@minnie.tuhs.org
https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-02-02  8:47 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <0f83f174-eeca-30fb-7b98-77fb0da80f2e@gmail.com>
     [not found] ` <CAC20D2Nh0t9dxVbRvXFxXkCfEaWkmp9MP1Xf+=YC3rfXf3SK3g@mail.gmail.com>
     [not found]   ` <9E47A62E-3AAD-491E-9164-3DCAD22EC1F7@kdbarto.org>
     [not found]     ` <CAGGBd_r24ODfR9oX_sMHkDWOotz9Bhup=CgDEgC=NNq9BFuNcg@mail.gmail.com>
     [not found]       ` <CAEoi9W6qovywr7KrJtXx5s-MKhC19pj5-VqQ0_1zoT-MaWRdSA@mail.gmail.com>
     [not found]         ` <71ce6652-cf15-44db-01df-62ab89a5a134@gmail.com>
     [not found]           ` <alpine.DEB.2.21.2201301944370.17970@sd-119843.dedibox.fr>
     [not found]             ` <CABH=_VS7G1XqO03NRkvSXEr8EiHWWP_sGyRnVNxV9wt3G9W_EQ@mail.gmail.com>
2022-02-02  4:53               ` [COFF] [TUHS] Compilation "vs" byte-code interpretation, was Re: Looking back to 1981 - what pascal was popular on what unix? Adam Thornton
2022-02-02  8:46       ` [COFF] " Peter Jeremy via COFF

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).