Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: Computer Old Farts Followers <coff@tuhs.org>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [COFF] Re: [TUHS] History of non-Bell C compilers?
Date: Fri, 8 Mar 2024 10:44:08 -0500	[thread overview]
Message-ID: <CABH=_VTbcd8NmAeU5+SpwgeLe845C5F3z9po1aF0p_5RHYnfOQ@mail.gmail.com> (raw)
In-Reply-To: <CANxB0bRF9WqY8=tLXGUfeFQGjqHfYVZ-hFDngn+kDL_Hr6pWrg@mail.gmail.com>

On 3/7/24, Tom Lyon <pugs78@gmail.com> wrote:
> For no good reason, I've been wondering about the early history of C
> compilers that were not derived from Ritchie, Johnson, and Snyder at Bell.
> Especially for x86.  Anyone have tales?
> Were any of those compilers ever used to port UNIX?
>
[topic of interest to COFF, as well, I think]

DEC's Ultrix for VAX and MIPS used off-the-shelf Unix cc.  I don't
recall what they used for Alpha.

The C compiler for VAX/VMS was written by Dave Cutler's team at
DECwest in Seattle.  The C front end generated intermediate language
(IL) for Cutler's VAX Code Generator (VCG), which was designed to be a
common back end for DEC's compilers for VAX/VMS.  His team also
licensed the Freiburghouse PL/I front end (commercial version of a
PL/I compiler originally done for Multics) and modified it to generate
VCG IL.  The VCG was also the back end for DEC's Ada compiler.  VCG
was superseded by the GEM back end, which supported Alpha and Itanium.
A port of GEM to x86 was in progress at the time Compaq sold off the
Alpha technology (including GEM and its C and Fortran front ends) to
Intel.

           reply	other threads:[~2024-03-08 15:44 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CANxB0bRF9WqY8=tLXGUfeFQGjqHfYVZ-hFDngn+kDL_Hr6pWrg@mail.gmail.com>]

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=_VTbcd8NmAeU5+SpwgeLe845C5F3z9po1aF0p_5RHYnfOQ@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=coff@tuhs.org \
    --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).