The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Greg 'groggy' Lehey <grog@lemis.com>
To: Paul Winalski <paul.winalski@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Tandem NSK implementation language (was: Happy birthday, John Backus!)
Date: Wed, 5 Dec 2018 09:49:25 +1100	[thread overview]
Message-ID: <20181204224925.GB55383@eureka.lemis.com> (raw)
In-Reply-To: <CABH=_VSewc0u6ef8SsGE=GjmMSBm4Fv-Wj+WFFaenwHjWF38_g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1524 bytes --]

On Tuesday,  4 December 2018 at 15:59:46 -0500, Paul Winalski wrote:
> On 12/4/18, Paul Winalski <paul.winalski@gmail.com> wrote:
>>
>> Over the years GEM was targeted to MIPS, PRISM, Alpha, and Itanium
>> machine architectures, and VMS, Unix, Linux, and Windows NT operating
>> systems.  We were working on x86 when Compaq sold the Alpha
>> architecture and its engineering team (including GEM) to Intel.
>
> I forgot one:  Tandem NonStop OS on Alpha, which was under development
> at Compaq at the time that Compaq decided to sell off the Alpha
> technology to Intel.

Was this a start-from-scratch operation?  The original Tandem OS
(called Guardian at the time) was written in Tandem's TAL (Transaction
Application Language, amongst other productions), a vague evolution of
HP's SPL that looked more like Algol, starting in about 1974.  That is
also the earliest I know of an operating system being implemented
entirely in a high level language.

When Tandem started using other architectures (MIPS) in the late 1980s
we discussed translating the whole thing to C.  I was asked to write a
99% translator (maintaining comments and such), and failed.

I lost track of the system after that, but it seems surprising that
they would have started again from scratch.

Greg
--
Sent from my desktop computer.
Finger grog@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA

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

  reply	other threads:[~2018-12-04 22:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04 14:43 [TUHS] Happy birthday, John Backus! Noel Chiappa
2018-12-04 14:53 ` Clem Cole
2018-12-04 16:24   ` Tim Rylance
2018-12-04 16:53     ` Clem Cole
2018-12-04 17:46       ` Paul Winalski
2018-12-04 20:59         ` Paul Winalski
2018-12-04 22:49           ` Greg 'groggy' Lehey [this message]
2018-12-05  0:08             ` [TUHS] Tandem NSK implementation language (was: Happy birthday, John Backus!) Paul Winalski
2018-12-05 17:49         ` [TUHS] Happy birthday, John Backus! Paul Winalski
2018-12-04 15:18 ` Toby Thain
     [not found] <mailman.1.1543975201.8252.tuhs@minnie.tuhs.org>
2018-12-05  4:48 ` [TUHS] Tandem NSK implementation language (was: Happy birthday, John Backus!) Paul McJones
2018-12-05  8:16   ` Dr Iain Maoileoin
2018-12-05 14:29   ` Clem Cole

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=20181204224925.GB55383@eureka.lemis.com \
    --to=grog@lemis.com \
    --cc=paul.winalski@gmail.com \
    --cc=tuhs@tuhs.org \
    /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).