From: "Aram Hăvărneanu" <aram.h@mgk.ro>
To: Tom Ivar Helbekkmo <tih@hamartun.priv.no>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Lost Origins of the Plan 9 C Compiler
Date: Fri, 5 Jan 2024 12:47:50 +0200 [thread overview]
Message-ID: <CAEAzY39NENh22o0cT43iP8BqZ2vEyXU4hJvo88GsOW+KWNAY1g@mail.gmail.com> (raw)
In-Reply-To: <m2zfxkf4x7.fsf@thuvia.hamartun.priv.no>
> 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
next prev parent reply other threads:[~2024-01-05 10:48 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 [this message]
2024-01-05 11:33 ` Rob Pike
2024-01-05 19:16 ` Michaelian Ennis
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=CAEAzY39NENh22o0cT43iP8BqZ2vEyXU4hJvo88GsOW+KWNAY1g@mail.gmail.com \
--to=aram.h@mgk.ro \
--cc=tih@hamartun.priv.no \
--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).