From: "Charles H. Sauer" <sauer@technologists.com>
To: Dan Cross <crossd@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] IBM RT/PC compilers [was Re: Any Bell 8-bit UNIX Efforts?
Date: Tue, 28 Feb 2023 21:02:17 -0600 [thread overview]
Message-ID: <1F9F6472-6F10-4E5D-81A4-BC0C6EB1F5BE@technologists.com> (raw)
In-Reply-To: <CAEoi9W7kjOZUBYB2fy1+=s111PS6K1V7Uzg2++QTD1gGF0arQQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]
> On Feb 28, 2023, at 8:35 PM, Dan Cross <crossd@gmail.com> wrote:
>
> On Tue, Feb 28, 2023 at 9:07 PM Ronald Natalie <ron@ronnatalie.com> wrote:
>> [snip]
>> At least it didn’t come with a prayer book like the Metalware compiler (which really needed all the divine intervention that it could get).
>
> Was that the one that shipped with the IBM RT? Is it just my
> imagination or did some of the error messages contain biblical
> references?
>
> - Dan C.
It may be that Metaware was available for AIX on the RT, but, if so, not bundled with AIX. AIX 1 releases bundled a fairly vanilla pcc as provided by ISC. AIX 2 releases bundled pcc with the HCR optimization phase added. I’m not sure about AIX 3 and beyond, since I left before they were released. The “strategic” plan was a reimplementation of the PL.8 compiler as a C compiler with the work done by an IBM group in Toronto. I suspect that was extra cost option and that pcc with HCR was still bundled in the base. I have the impression that AOS (BSD for RT) eventually also included the HCR phase. See https://notes.technologists.com/notes/2017/03/08/lets-start-at-the-very-beginning-801-romp-rtpc-aix-versions/ for more context. CHS
--
voice: +1.512.784.7526 e-mail: sauer@technologists.com <mailto:sauer@technologists.com>
fax: +1.512.346.5240 web: https://technologists.com/sauer/ <http://technologists.com/sauer/>
Facebook/Google/LinkedIn/Twitter: CharlesHSauer
[-- Attachment #2: Type: text/html, Size: 3263 bytes --]
next prev parent reply other threads:[~2023-03-01 3:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 19:48 [TUHS] " segaloco via TUHS
2023-02-27 3:55 ` [TUHS] " Warner Losh
2023-02-27 10:57 ` Jonathan Gray
2023-02-28 18:59 ` segaloco via TUHS
2023-02-28 19:03 ` Larry McVoy
2023-02-28 19:42 ` Clem Cole
2023-02-28 19:57 ` Bakul Shah
2023-02-28 23:31 ` Dave Horsfall
2023-03-01 0:39 ` Larry McVoy
2023-03-01 1:21 ` Rich Salz
2023-03-01 1:27 ` Warner Losh
2023-03-01 2:07 ` Ronald Natalie
2023-03-01 2:35 ` Dan Cross
2023-03-01 2:38 ` Ronald Natalie
2023-03-01 3:02 ` Charles H. Sauer [this message]
2023-03-01 4:02 ` [TUHS] Re: IBM RT/PC compilers [was " George Michaelson
2023-03-01 14:12 ` [TUHS] " Chet Ramey
2023-03-02 9:05 ` Jaap Akkerhuis via TUHS
2023-03-02 19:26 ` Clem Cole
2023-03-01 2:50 ` Jonathan Gray
2023-03-01 0:31 ` Jonathan Gray
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=1F9F6472-6F10-4E5D-81A4-BC0C6EB1F5BE@technologists.com \
--to=sauer@technologists.com \
--cc=crossd@gmail.com \
--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).