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: Sun, 25 Apr 2021 16:54:32 -0400 [thread overview]
Message-ID: <CAEoi9W4L1zAK_169KVaKiq0X7byuLwre+KPT7wHfXzqqcA75-g@mail.gmail.com> (raw)
In-Reply-To: <20210425204842.3FAC4640CB6@lignose.oclsc.org>
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
I seem to recall that LCC was also used, at least on 10th Ed. Am I
imagining things, or was that real?
On Sun, Apr 25, 2021 at 4:51 PM Norman Wilson <norman@oclsc.org> wrote:
> I was waiting to see whether Steve Johnson would speak
> up, because I'm not much of an expert; but yes, the VAX
> C compiler in V8/V9/V10 is pcc2.
>
> I think there are a few Research-specific hacks to add
> additional stab info for pi(9.1) and on request insert
> basic-block profiling for lcomp(1), but nothing major.
>
> Maybe we did some hacking on c2 as well. I know I did
> a lot of c2 cleanup later in my personal hacking in
> Toronto, but I don't think I did much if any in New
> Jersey. But that's independent of the compiler (modulo,
> I think, some of my later fixes discovered by using c2
> with a different compiler).
>
> Norman Wilson
> Toronto ON
>
[-- Attachment #2: Type: text/html, Size: 1188 bytes --]
next prev parent reply other threads:[~2021-04-25 20:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-25 20:48 Norman Wilson
2021-04-25 20:54 ` Dan Cross [this message]
2021-04-26 6:29 ` Noel Hunt
-- 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 22:02 Norman Wilson
2021-04-26 0:18 ` Nemo Nusquam
2021-04-26 16:51 ` Adam Thornton
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=CAEoi9W4L1zAK_169KVaKiq0X7byuLwre+KPT7wHfXzqqcA75-g@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).