The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: "tuhs@minnie.tuhs.org" <tuhs@minnie.tuhs.org>
Subject: [TUHS] DEC's MIPS product (was  If not Linux, then what?)
Date: Wed, 28 Aug 2019 15:14:42 -0400	[thread overview]
Message-ID: <CABH=_VTmj5DOggtpFL4eH1VwVsDZJHFeJnzod_UwR90QAU7jTA@mail.gmail.com> (raw)

On 8/28/19, Clem Cole <clemc@ccc.com> wrote:
>
> So, I think the MIPS product was a holding pattern while DEC got it's
> strategy together. Alpha would really show up until later (I would leave
> LCC and go to DEC to be apart if that).   Also note Alpha was brought
> up/debugged on Ultrix and of course, Prism sort of had Ultrix on it.    But
> I think using the MIPS chip keep them in the game, when Vax was dying and
> RISC was the word on the street.

I was in DEC's compiler development team at the time, working on the
new GEM common back end, and this matches my recollection.  The
original plan was for GEM to be the successor to the VAX Code
Generator (VCG, the common back end used by DEC's PL/I, Ada, C/C++ and
a few other compilers on VAX/VMS) and its first target was the VMS
personality module Prism's OS, Mica.  Prism was close to delivering
silicon when it was cancelled in favor of Alpha.  DEC's MIPS-based
products were done as a stopgap until Alpha was ready.  The GEM group
implemented a MIPS code generator.  I don't recall whether we actually
shipped any GEM-based products on the MIPS/Ultrix platform.  GEM
focused on Alpha (on VMS, Unix, and Windows host and target platforms)
shortly thereafter.

-Paul W.

                 reply	other threads:[~2019-08-28 19:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CABH=_VTmj5DOggtpFL4eH1VwVsDZJHFeJnzod_UwR90QAU7jTA@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=clemc@ccc.com \
    --cc=tuhs@minnie.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).