From: norman@oclsc.org (Norman Wilson)
To: tuhs@tuhs.org
Subject: Re: [TUHS] pcc in 8th edition
Date: Sun, 25 Apr 2021 18:02:26 -0400 (EDT) [thread overview]
Message-ID: <20210425220226.A7E5E640CB6@lignose.oclsc.org> (raw)
Dan Cross:
I seem to recall that LCC was also used, at least on 10th Ed. Am I
imagining things, or was that real?
===
Some of the earliest work on lcc was done in 1127; Chris
Fraser worked for the Labs for some years, Dave Hanson
collaborated from his appointment at Princeton. I believe
there was a /usr/bin/lcc. Some programs used it, either
because they needed some part of the ISO syntax (pcc2 was
pre-ISO) or just because.
I don't think that version of lcc used Reiser's c2 optimizer;
it generated reasonably good code by itself, including
emitting auto-increment/decrement instructions. Later
versions of lcc (such as that I later adopted as cc in
my personal V10 world) couldn't do that any more, so I
had to keep c2, and in fact to modify it to turn
addl3 a,b,(p)
mova 4(p),p
into
addl3 a,b,(p)+
(or maybe it was addl2 $4,p, I forget)
But that's another story which I'll tell only if asked,
and nothing to do with the original question.
next reply other threads:[~2021-04-25 22:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-25 22:02 Norman Wilson [this message]
2021-04-26 0:18 ` Nemo Nusquam
2021-04-26 16:51 ` Adam Thornton
-- strict thread matches above, loose matches on Subject: below --
2021-04-26 18:00 Norman Wilson
2021-04-26 18:11 ` Dan Cross
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=20210425220226.A7E5E640CB6@lignose.oclsc.org \
--to=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).