The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Marc Rochkind <mrochkind@gmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: History of non-Bell C compilers?
Date: Thu, 7 Mar 2024 17:30:24 -0700	[thread overview]
Message-ID: <CAOkr1zWuTvEEj4i8FZQEE2cH9vcQJPLvEdt8kP7a=199fb29AQ@mail.gmail.com> (raw)
In-Reply-To: <1d208136-cf1b-4cbf-8401-aa0b95971372@technologists.com>

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

Larry & Dave, thanks for jogging my memory. I'm pretty sure it was BDS C on
that z80 Zenith computer. (See my longer post above.)

I should add that around 1984 I got a copy of PC/IX for the IBM XT,
directly from Interactive Systems in Santa Monica, where I knew a few
people. That was true UNIX, System III, I think, and I used it for all of
the examples for my book "Advanced UNIX Programming," which came out in
1985. It, of course, had a real Bell Labs C compiler.

Marc

On Thu, Mar 7, 2024 at 5:15 PM Charles H Sauer (he/him) <
sauer@technologists.com> wrote:

> On 3/7/2024 5:52 PM, Warner Losh wrote:
> >
> >
> > On Thu, Mar 7, 2024 at 4:24 PM Warner Losh <imp@bsdimp.com
> > <mailto:imp@bsdimp.com>> wrote:
> >
> >
> >
> >     On Thu, Mar 7, 2024, 4:14 PM Tom Lyon <pugs78@gmail.com
> >     <mailto: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?
> >
> >
> >     MIT had several that were used for ka9q and at least the Venix x86
> >     port. They supported the popular micros of the time. Various
> >     versions of them survive to the present day.
> >
> >
> > It's at bitsavers:
> >
> > https://bitsavers.org/bits/MIT/pc-ip/8086_C_19850820.tar
> > <https://bitsavers.org/bits/MIT/pc-ip/8086_C_19850820.tar>
> > and
> > https://bitsavers.org/bits/MIT/trix/MIT_Compiler_Tape/
> > <https://bitsavers.org/bits/MIT/trix/MIT_Compiler_Tape/>
> >
> > are pointers to compilers from the early 80s. Obviously not ANSI-C
> > compilers :)
> >
> > Warner
>
> See, also,
> https://www.program-transformation.org/Transform/CCompilerHistory.html &
> http://www.desmet-c.com/.
>
> When I only had PC/IX on an XT at my office and a PCjr at home, I mostly
> worked with C at home with DeSmet. I still have a couple of 5.25" 360K
> diskettes labeled C-Ware, which I think are DeSmet 2.4.
>
> Charlie
>
> --
> voice: +1.512.784.7526       e-mail: sauer@technologists.com
> fax: +1.512.346.5240         Web: https://technologists.com/sauer/
> Facebook/Google/LinkedIn/Twitter
> <https://technologists.com/sauer/Facebook/Google/LinkedIn/Twitter>:
> CharlesHSauer
>


-- 
*My new email address is mrochkind@gmail.com <mrochkind@gmail.com>*

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

  reply	other threads:[~2024-03-08  0:30 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07 23:14 [TUHS] " Tom Lyon
2024-03-07 23:24 ` [TUHS] " Warner Losh
2024-03-07 23:39   ` Dave Horsfall
2024-03-07 23:49     ` Larry McVoy
2024-03-07 23:56       ` Luther Johnson
2024-03-08 14:03         ` John Foust via TUHS
2024-03-07 23:59       ` Greg 'groggy' Lehey
2024-03-08  0:08         ` Rich Salz
2024-03-08  0:30           ` Warner Losh
2024-03-08  0:57             ` Rob Pike
2024-03-08  1:08               ` Bakul Shah via TUHS
2024-03-08  1:10                 ` Rob Pike
2024-03-08  1:12                   ` Rob Pike
2024-03-08  1:22                     ` Bakul Shah via TUHS
2024-03-08  9:33               ` arnold
2024-03-08  9:45                 ` Wesley Parish
2024-03-08 13:06                   ` Luther Johnson
2024-03-08 18:33               ` William H. Mitchell
2024-03-10  3:14                 ` Adam Thornton
2024-03-11 22:21       ` Phil Budne
2024-03-07 23:52   ` Warner Losh
2024-03-08  0:15     ` Charles H Sauer (he/him)
2024-03-08  0:30       ` Marc Rochkind [this message]
2024-03-08  0:54         ` Heinz Lycklama
2024-03-08  1:48           ` segaloco via TUHS
2024-03-08  2:12             ` Tom Lyon
2024-03-08  2:13     ` Lawrence Stewart
2024-03-08  3:15     ` Jonathan Gray
2024-03-07 23:24 ` Luther Johnson
2024-03-07 23:27   ` Luther Johnson
2024-03-07 23:44     ` Tom Lyon
2024-03-08  0:24       ` Marc Rochkind
2024-03-08  1:27         ` Jeffry R. Abramson
2024-03-10  2:13         ` Greg A. Woods
2024-03-08  2:26 ` Will Senn
2024-03-08  3:03   ` Peter Yardley
2024-03-08  3:28 ` George Michaelson
2024-03-08  3:58   ` Luther Johnson
2024-03-08  5:53 ` Lars Brinkhoff
2024-03-08 13:42 ` Henry Bent
2024-03-08 14:00   ` arnold
2024-03-08 14:16   ` Warner Losh
2024-03-08 15:44 ` Paul Winalski
2024-03-08 17:18   ` Adam Thornton
2024-03-10  2:31 ` Damian Wildie
2024-03-11 17:12 Paul Ruizendaal
2024-03-11 20:44 ` Marc Rochkind
2024-03-11 22:28   ` Peter Yardley
2024-03-12  0:30     ` ron minnich
2024-03-12 13:31       ` Larry Stewart
2024-03-12 16:41     ` Paul Winalski
2024-03-12 14:55   ` Henry Bent
2024-03-12 17:17     ` Marc Rochkind
2024-03-13 14:37       ` Clem Cole
2024-03-13 15:28         ` Marc Rochkind
2024-03-13 15:33           ` Warner Losh
2024-03-13 15:53           ` Clem Cole
2024-03-12 15:42 ` Paul Ruizendaal
2024-03-12 23:08 Steve Simon
     [not found] <aee297f1-2f6a-4620-87f7-f1672ae03b61@osta.com>
2024-03-15  3:34 ` Heinz Lycklama

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='CAOkr1zWuTvEEj4i8FZQEE2cH9vcQJPLvEdt8kP7a=199fb29AQ@mail.gmail.com' \
    --to=mrochkind@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).