The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Henry Bent <henry.r.bent@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] DEC compilers (was Happy birthday, John Backus!)
Date: Wed, 5 Dec 2018 13:46:44 -0500	[thread overview]
Message-ID: <CAC20D2PnjAM=OSsjwktriS_BmAUwaCcRsLwPKm6A8mSmf362jw@mail.gmail.com> (raw)
In-Reply-To: <CAEdTPBcbh241896vNTgsBGU20g6a_MDQ1ikJQf+bAx_DNOAyoQ@mail.gmail.com>

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

On Wed, Dec 5, 2018 at 1:29 PM Henry Bent <henry.r.bent@gmail.com> wrote:

>
> http://bitsavers.trailing-edge.com/pdf/dec/vax/ultrix-32/4.0_Jun90/AA-MG63B-TE_ULTRIX_Technical_Summary_Jun90.pdf
> seems to imply that as of Ultrix 4.0, there were COBOL and Ada compilers
> for the VAX (Table 4-1).  Elsewhere VAX LISP for Ultrix is mentioned, which
> I had no idea existed.  I hope that these compilers have been preserved
> somewhere, as I imagine they sold in relatively small quantities.
>
It all gets fuzzy by then - what was released and what actually existed.
 Their was a Vax LISP from the Franz guys, but I think the DEC/CMU Common
LISP was VMS also was there.     The 11 has been dropped from support an
the PMAX has replaced it but the compilers for PMAX are coming primarily
from MIPS.   I do not believe DEC did a LISP themselves for the MIPS
machines.  But, it turns out a number of the MIPS compilers would work on
Ultrix, although DEC had not released them directly.   But some 3rd parties
did on their own, sometimes with DEC's blessing and sometimes not.
 Plus the Alpha is being developed by then, so TLG is up to neck in the GEM
development cycle which would replace everything i the languages teams when
the dust settled (as Paul has mentioned it was an amazing piece of work at
the time and still somewhat lasts today - the VMS,Inc folks of course are
built an INTEL*64 code generator for it and supposedlty have VMS booting on
modern HW these days).

Clem
ᐧ

[-- Attachment #2: Type: text/html, Size: 2711 bytes --]

  reply	other threads:[~2018-12-05 18:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05 16:24 Paul Winalski
2018-12-05 16:46 ` Paul Winalski
2018-12-05 17:06   ` Warner Losh
2018-12-05 17:58   ` Clem Cole
2018-12-05 18:16     ` Paul Winalski
2018-12-05 18:26     ` Henry Bent
2018-12-05 18:46       ` Clem Cole [this message]
2018-12-05 18:56         ` Lars Brinkhoff
2018-12-05 19:15         ` Paul Winalski
2018-12-05 21:35           ` Arrigo Triulzi
2018-12-07 19:03             ` Paul Winalski
2018-12-05 19:13 Norman Wilson

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='CAC20D2PnjAM=OSsjwktriS_BmAUwaCcRsLwPKm6A8mSmf362jw@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=henry.r.bent@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).