The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Michaelian Ennis <mennis@corvus.net>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Lost Origins of the Plan 9 C Compiler
Date: Fri, 5 Jan 2024 11:16:30 -0800	[thread overview]
Message-ID: <CALHNQMT98de8x18FjzwGayixNeJWkBXq_e-hiKSwBA=z3jy1AA@mail.gmail.com> (raw)
In-Reply-To: <CAKzdPgwb7B7VMY6MBpnOPbhqZYLZO4=inB=UXEcbWBA4v1-Bxg@mail.gmail.com>

There is additional context about what was happening at the time in
Rob's talk at GopherCon 2016: Rob Pike - The Design of the Go
Assembler .

Ian


On Fri, Jan 5, 2024 at 3:34 AM Rob Pike <robpike@gmail.com> wrote:
>
> You shouldn't dismiss so lightly. The cited document answers the question of the first target, which was the National 32000. It ran on a Sequent multiprocessor, a machine we were thinking about using for other work.
>
> So no, it was not created on Research Unix, or at least not for it. We wanted a faster compiler for a number of reasons, and Ken had ideas about that. Because of its architecture, it was easy to port to other RISC architectures, such as the MIPS and SPARC, although both those machines had wrinkles that needed ironing out.
>
> -rob
>
>
> On Fri, Jan 5, 2024 at 10:05 PM Aram Hăvărneanu <aram.h@mgk.ro> wrote:
>>
>> > I think this may be what you are looking for:
>> > http://doc.cat-v.org/bell_labs/new_c_compilers/
>>
>> Since I have worked on a derivative of the Plan 9 C compiler, I
>> assure you I have read all the available papers and documentation
>> about it and they answer none of the questions raised above.
>>
>> --
>> Aram Hăvărneanu

      reply	other threads:[~2024-01-05 19:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05 10:24 [TUHS] " Aram Hăvărneanu
2024-01-05 10:30 ` [TUHS] " Tom Ivar Helbekkmo via TUHS
2024-01-05 10:47   ` Aram Hăvărneanu
2024-01-05 11:33     ` Rob Pike
2024-01-05 19:16       ` Michaelian Ennis [this message]

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='CALHNQMT98de8x18FjzwGayixNeJWkBXq_e-hiKSwBA=z3jy1AA@mail.gmail.com' \
    --to=mennis@corvus.net \
    --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).