The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] fortran compiler, in assembly, for pdp-11
Date: Tue, 7 Mar 2017 16:05:07 -0500	[thread overview]
Message-ID: <CAC20D2NU4kktOQSJo2GMd5QE+TQ1+mqjnGvmtFCPbiVs4tk7vA@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W5Pa1jG45YoZ-VsSGbPB36EHrMEUX71hXq-Lm52nt253A@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]

On Tue, Mar 7, 2017 at 2:53 PM, Dan Cross <crossd at gmail.com> wrote:

> /usr/source/fort


​Ah - that is the old Research compiler before f77.   I'm not even sure it
will compile a full Fortran-IV deck.   As I said, pretty early into USENIX
look in the CULC directory and you should find a FTN compiler and the DEC
assembler. That was the compiler many of used until the pcc/f77 showed up.

Years later, when DEC released Ultrix, the languages groups formally
supported Ultrix.  Besides being more modern versions of the compilers, is
they supported the old VMS linker, which was ported to both the 11 and the
Vax by Paul Winalski. ​  Not only did he get it run on Unix, he got it work
with a.out, and macho files too.  I don't remember if he could grok ELF
with it (he would know - maybe I can convince to join this list).   He will
carry a lot of DEC history in the middle times, when I was doing startups.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170307/657ce454/attachment-0001.html>


  parent reply	other threads:[~2017-03-07 21:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07 17:34 ron minnich
2017-03-07 18:13 ` ron minnich
2017-03-07 19:37   ` Ron Natalie
2017-03-07 19:53     ` Dan Cross
2017-03-07 20:03       ` Paul Ruizendaal
2017-03-07 21:05       ` Clem Cole [this message]
2017-03-07 19:40   ` Clem Cole
2017-03-07 19:55     ` Clem Cole
2017-03-07 20:41       ` Dave Horsfall

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=CAC20D2NU4kktOQSJo2GMd5QE+TQ1+mqjnGvmtFCPbiVs4tk7vA@mail.gmail.com \
    --to=clemc@ccc.com \
    /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).