The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Phil Budne <phil@ultimate.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: History of non-Bell C compilers?
Date: Mon, 11 Mar 2024 18:21:37 -0400	[thread overview]
Message-ID: <202403112221.42BMLbd0091200@ultimate.com> (raw)
In-Reply-To: <20240307234921.GO2252@mcvoy.com>

On Thu, 7 Mar 2024 Larry McVoy wrote:
> My memory is BDS C did C just fine, but had a very non standard standard
> I/O library.  I had relearn stdio when I got to Unix.  But I never had a
> problem with it not compiling C.

Early on (originally?) a question asked was "what non-AT&T origin
compilers were used to compile Unix.  Two non-AT&T compilers I
remember wrangling with on U in the 1980's were Green Hills (on the
Encore Multimax), and another compiler on some early flavor of ROMP or
Power based IBM workstation.  Maybe it was xlc?

I remember one of them was unaware that case labels are valid ANYWHERE
inside of a switch statement (the feature Duff applied so cleverly),
something I discovered trying to bring up cfront (the original
C++/C-with-classes compiler, that output C).

On BDS C, I remember chatting with Leor Zolman: he was looking to
contract someone to port BDS (Brain Damage Systems) C to the PC, but
it was written in assembly language, so it wasn't a particularly
attractive job.  I don't recall him having a _particularly_ high
opinion of the code, but I could be misremembering.

  parent reply	other threads:[~2024-03-11 22:21 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 [this message]
2024-03-07 23:52   ` Warner Losh
2024-03-08  0:15     ` Charles H Sauer (he/him)
2024-03-08  0:30       ` Marc Rochkind
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=202403112221.42BMLbd0091200@ultimate.com \
    --to=phil@ultimate.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).