The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: SHOPPA@TRAILING-EDGE.COM (SHOPPA@TRAILING-EDGE.COM)
Subject: [pups] Re: GCC
Date: Sat, 19 Jan 2002 9:54:35 -0500	[thread overview]
Message-ID: <020119095435.21e004b5@TRAILING-EDGE.COM> (raw)

Johnny Billquist <bqt at update.uu.se> writes:
> DECUS C might be a better starting point.

DECUS C is kind-of a funny case.  Whereas most C compilers are
traditionally maintained and distributed as C source code, DECUS C
is distributed and maintained in PDP-11 assembly language.

For other C compilers, a significant milestone was when they were
rewritten in C and compiled themselves.  DECUS C is the odd guy out because
it never tried to reach this milestone.  In some sense this is a good thing,
because it lets you build it on a machine without any access to any C compiler.

Tim.



             reply	other threads:[~2002-01-19 14:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-19 14:54 SHOPPA [this message]
2002-01-19 15:12 ` Johnny Billquist
  -- strict thread matches above, loose matches on Subject: below --
2002-01-19 16:22 Davidson, Steve
2002-01-18 22:29 bwc
2002-01-19  0:08 ` Bill Gunshannon
2002-01-18 22:13 norman
     [not found] <no.id>
2002-01-18  6:53 ` Aaron J. Grier
2002-01-18  7:07   ` Wilko Bulte
2002-01-18  9:06     ` Lars Brinkhoff
2002-01-18 12:44   ` Warren Toomey
2002-01-18 14:49     ` Bill Gunshannon
2002-01-18 15:31       ` Lars Brinkhoff
2002-01-18 19:00       ` Johnny Billquist
2002-01-18 21:54         ` Jonathan Engdahl
2002-01-19  8:48         ` Lars Brinkhoff
2002-01-19 21:19           ` Warren Toomey
2002-01-18 18:06     ` Aaron J. Grier

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=020119095435.21e004b5@TRAILING-EDGE.COM \
    --to=shoppa@trailing-edge.com \
    /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).