The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: (Norman Wilson)
Subject: Re: [TUHS] pcc in 8th edition
Date: Mon, 26 Apr 2021 14:00:51 -0400 (EDT)
Message-ID: <> (raw)

Adam Thornton:

  I sat in on an undergrad course from [Dave Hanson] my first year of
  grad school (94-95) and he taught it with lcc.  I asked `why not
  gcc' and he said, `gcc is 100,000 lines and I don't know what 90%
  of them are doing; lcc is 10,000'.


My copy is indeed about 10K lines, not counting the code-generator
modules.  Those are C files generated by a utility program lburg
from a template file.  The three architectures supplied in the
distribution, for MIPS, SPARC, and X86, have template files of
about 900, 1200, and 700 lines respectively.

The template file for the VAX is about 2800 lines, but includes
some metalanguage of my own, interpreted by an awk script, to
generate extra rules for all the direct-store type-to-type
instructions.  The C output from lburg for the other architectures
is 5000-6000 lines; for the VAX, after expansion by my awk
program and then by lburg, is nearly 20K.

Did someone say Complex Instruction Set?

Norman Wilson
Toronto ON

             reply	other threads:[~2021-04-26 18:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26 18:00 Norman Wilson [this message]
2021-04-26 18:11 ` Dan Cross
  -- strict thread matches above, loose matches on Subject: below --
2021-04-25 22:02 Norman Wilson
2021-04-26  0:18 ` Nemo Nusquam
2021-04-26 16:51 ` Adam Thornton
2021-04-25 20:48 Norman Wilson
2021-04-25 20:54 ` Dan Cross
2021-04-26  6:29 ` Noel Hunt
2021-04-25 12:35 Paul Ruizendaal
2021-04-25 12:49 ` arnold
2021-04-25 14:04   ` Paul Ruizendaal
2021-04-25 15:45   ` Paul Ruizendaal
2021-04-25 17:11     ` Clem Cole
2021-04-25 17:32       ` arnold
2021-04-25 17:46         ` Clem Cole
2021-04-25 20:11       ` Paul Ruizendaal
2021-04-30 23:08       ` Paul Ruizendaal
2021-04-25  9:15 Paul Ruizendaal via TUHS

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

The Unix Heritage Society mailing list

This inbox may be cloned and mirrored by anyone:

	git clone --mirror

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 tuhs tuhs/ \
	public-inbox-index tuhs

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone