The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: Norman Wilson <norman@oclsc.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] pcc in 8th edition
Date: Mon, 26 Apr 2021 14:11:42 -0400	[thread overview]
Message-ID: <CAEoi9W4GyvgBFYht5kCb9RqT-=kpzcyR0ngqtuTgGyGP9OiVSg@mail.gmail.com> (raw)
In-Reply-To: <20210426180051.D39DA640CB6@lignose.oclsc.org>

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

On Mon, Apr 26, 2021 at 2:03 PM Norman Wilson <norman@oclsc.org> wrote:

> 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?
>

Indeed!

https://yarchive.net/comp/vax.html

I recall one of Mashey's posts talking about the number of page faults that
_might_ arise from execution of one instance of one of the more baroque VAX
instructions. It was something like 40 (!!).

        - Dan C.

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

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

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-26 18:00 Norman Wilson
2021-04-26 18:11 ` Dan Cross [this message]
  -- 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:
  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='CAEoi9W4GyvgBFYht5kCb9RqT-=kpzcyR0ngqtuTgGyGP9OiVSg@mail.gmail.com' \
    --to=crossd@gmail.com \
    --cc=norman@oclsc.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).