From: Dennis Boone <drb@msu.edu>
To: tuhs@tuhs.org
Subject: Re: [TUHS] History of m6?
Date: Mon, 11 Nov 2019 19:42:25 -0500 [thread overview]
Message-ID: <20191112004225.CA53E297745@yagi.h-net.msu.edu> (raw)
In-Reply-To: (Your message of Mon, 11 Nov 2019 19:30:47 -0500.) <EBCBF73F-3CF2-45F2-B062-42152AA01FC9@ccc.com>
> Not so fast there my friend. Ratfor was used a great deal. For
> instance The PGI compiler folks wrote a parallel optimizing compiler
> for the FPS-164 in it. And FPS used it for there OS. Plus Apollo
> wrote all their original utilities in it.
The Software Tools stuff too, including the STVOS stuff Berkeley
managed. If you pick an old platform and count RATFOR implementations,
all of them seem to have enough of them you can't swing a dead cat.
RATFOR may not be enjoyable in modern terms, but compared to building in
native F66...
De
next prev parent reply other threads:[~2019-11-12 0:42 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 21:10 Arnold Robbins
2019-11-11 22:18 ` Dennis Boone
2019-11-12 16:01 ` Leah Neukirchen
2019-11-11 22:31 ` Theodore Y. Ts'o
2019-11-11 22:58 ` Dave Horsfall
2019-11-12 0:07 ` Nemo Nusquam
2019-11-12 0:39 ` Dave Horsfall
2019-11-12 0:30 ` Clem cole
2019-11-16 16:27 ` SPC
2019-11-17 5:30 ` Dave Horsfall
2019-11-17 5:50 ` Larry McVoy
2019-11-17 18:12 ` Bakul Shah
2019-11-17 18:23 ` Michael Kjörling
2019-11-17 18:56 ` Bakul Shah
2019-11-17 22:46 ` Barry Stanly
2019-11-12 0:42 ` Dennis Boone [this message]
2019-11-11 22:37 ` Michael Kjörling
2019-11-12 1:09 ` Steve Johnson
2019-11-12 15:07 ` Clem Cole
2019-11-13 9:16 ` Thomas Paulsen
2019-11-13 12:20 ` Lars Brinkhoff
2019-11-13 12:50 ` Mike Markowski
2019-11-13 13:02 ` Lars Brinkhoff
2019-11-13 16:56 ` Paul Winalski
2019-11-13 19:19 ` Lars Brinkhoff
2019-11-13 19:21 ` Jon Steinhart
2019-11-14 9:26 ` Thomas Paulsen
2019-11-14 10:53 ` Lars Brinkhoff
2019-11-13 21:26 ` Dave Horsfall
2019-11-13 22:53 ` Jaap Akkerhuis
2019-11-12 15:15 Doug McIlroy
2019-11-13 7:38 ` arnold
2019-11-13 10:55 ` David Arnold
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=20191112004225.CA53E297745@yagi.h-net.msu.edu \
--to=drb@msu.edu \
--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).