The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: krewat@kilonet.net (Arthur Krewat)
Subject: [TUHS] Happy birthday, PDP-8!
Date: Mon, 27 Mar 2017 10:07:50 -0400	[thread overview]
Message-ID: <604a8a43-876d-20d7-e1df-41c7c5dd9c22@kilonet.net> (raw)
In-Reply-To: <20170327012440.B11AC18C085@mercury.lcs.mit.edu>

And how is that different than the Intel line of CPU's? Backward 
compatibility, while adding features as it progressed.

The KA10, KI10, KL10, KS10 all added something to the mix that their 
predecessors did not have.

To call something a "clone" infers a second party making as close of a 
copy as possible to the original. The KA10 was not a "clone" of a PDP-6.

http://www.ultimate.com/phil/pdp10/pdp6-vs-ka10



On 3/26/2017 9:24 PM, Noel Chiappa wrote:
>      > From: Arthur Krewat
>
>      >> The PDP-6 (of which the PDP-10 was a clone)
>
>      > Um. More like a natural progression.
>      > Like 8086->80186->80286->80386->80486->...
>
> No, the PDP-6 and PDP-10 have identical instruction sets, and in general, a
> program that will run on one, will run on the other. See "decsystem10 System
> Reference Manual" (DEC-10-XSRMA-A=D", pg. 2-72., which provides a 7-instruction
> code fragment which allows a program to work out if it's running on a PDP-6, a
> KA10, or a KI10.
>
> The KA10 is a re-implementation (using mostly B-series Flip Chips) of the
> PDP-6 (which was built out of System Modules - the predecessor to Flip Chips).
>
>         Noel
>



  reply	other threads:[~2017-03-27 14:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27  1:24 Noel Chiappa
2017-03-27 14:07 ` Arthur Krewat [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-03-21 21:52 Dave Horsfall
2018-03-21 21:59 ` George Michaelson
     [not found] <mailman.659.1490686648.3779.tuhs@minnie.tuhs.org>
2017-03-28 22:10 ` Johnny Billquist
2017-03-28  2:38 Noel Chiappa
     [not found] <mailman.1.1490580001.4973.tuhs@minnie.tuhs.org>
2017-03-27 23:30 ` Johnny Billquist
2017-03-27 23:33   ` Steve Nickolas
2017-03-27 23:49     ` Johnny Billquist
2017-03-27  0:31 Noel Chiappa
2017-03-27  0:37 ` Arthur Krewat
2017-03-27 12:05 ` Tim Bradshaw
2017-03-27 13:35   ` Tony Finch
2017-03-27 21:37   ` Terry Smith
2017-03-21 23:57 Atindra Chaturvedi
2017-03-21 21:34 Dave Horsfall
2017-03-22 16:34 ` Ron Natalie
2017-03-26 19:49   ` Dave Horsfall
2017-03-26 20:11     ` Paul Winalski
2017-03-26 22:20       ` Greg 'groggy' Lehey
2017-03-26 22:25     ` Greg 'groggy' Lehey

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=604a8a43-876d-20d7-e1df-41c7c5dd9c22@kilonet.net \
    --to=krewat@kilonet.net \
    /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).