The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ron@ronnatalie.com (Ron Natalie)
Subject: [TUHS] Unix on PDP8?
Date: Wed, 29 Nov 2017 09:31:44 -0500	[thread overview]
Message-ID: <00cf01d3691e$c80766e0$581634a0$@ronnatalie.com> (raw)
In-Reply-To: <7wr2sh60a9.fsf@junk.nocrew.org>

C itself is going to be difficult on the PDP-8.    Too much ingrained (and
now codified by ANSI/ISO) that requires shorts to be at least 16 bits and
longs to be at least 32 bits, neither of which the 8 supports well.
Even the EAE or FP modules only added limited 24 bit support.    

-----Original Message-----
From: TUHS [mailto:tuhs-bounces@minnie.tuhs.org] On Behalf Of Lars Brinkhoff
Sent: Wednesday, November 29, 2017 1:56 AM
To: Will Senn
Cc: Tuhs
Subject: Re: [TUHS] Unix on PDP8?

Will Senn wrote:
> Was Unix ever ported to a PDP8, or any other 12 bit environment, for 
> that matter?

There are Unix-like systems for 8-bit micros which might possibly be adapted
for PDP-8.  Lunix, UZI, FUZIX...

> I've been messing around in the PDP8 emulation world and enjoying the 
> excursion into simplified ISA and memory architectures.

The tiny instruction set is surprisingly versatile!



  parent reply	other threads:[~2017-11-29 14:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28 19:55 Will Senn
2017-11-28 20:24 ` Clem Cole
2017-11-28 23:26   ` Ron Natalie
2017-11-29  6:56 ` Lars Brinkhoff
2017-11-29 14:05   ` Clem Cole
2017-11-30  0:53     ` Robert Swierczek
2017-11-30  8:34     ` emanuel stiebler
2017-11-29 14:31   ` Ron Natalie [this message]
2017-11-29 22:11     ` Dave Horsfall
2017-11-29 22:28       ` Warren Toomey
2017-11-29 23:12         ` Dave Horsfall
2017-11-30  1:17     ` Robert Swierczek
2017-11-30  2:37       ` Dave Horsfall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='00cf01d3691e$c80766e0$581634a0$@ronnatalie.com' \
    --to=ron@ronnatalie.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).