The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: crossd@gmail.com (Dan Cross)
Subject: [TUHS] fortran compiler, in assembly, for pdp-11
Date: Tue, 7 Mar 2017 14:53:28 -0500	[thread overview]
Message-ID: <CAEoi9W5Pa1jG45YoZ-VsSGbPB36EHrMEUX71hXq-Lm52nt253A@mail.gmail.com> (raw)
In-Reply-To: <006901d2977a$41878350$c49689f0$@ronnatalie.com>

On Tue, Mar 7, 2017 at 2:37 PM, Ron Natalie <ron at ronnatalie.com> wrote:

> Dunno.   The first I dealt with was the f77 based on the pcc backend.
>

Hmm. I've found the source code for that compiler (/usr/source/fort in the
v6 distribution) but there doesn't seem to be an attribution.  The man page
seems to be dated 8/20/73, but again lacks attribution; perhaps Ken wrote
it?

        - Dan C.

*From:* TUHS [mailto:tuhs-bounces at minnie.tuhs.org] *On Behalf Of *ron
> minnich
> *Sent:* Tuesday, March 7, 2017 1:14 PM
> *To:* TUHS main list
> *Subject:* Re: [TUHS] fortran compiler, in assembly, for pdp-11
>
>
>
> I was not clear, evidently, although part of this is my memory's fault :-)
>
>
>
> There was a fortran compiler on v6, written in assembly. I was wondering
> who wrote it.
>
> On Tue, Mar 7, 2017 at 9:34 AM ron minnich <rminnich at gmail.com> wrote:
>
> I spent a year or so working on this in 1977. I was wondering who wrote it.
>
>
>
> Funny but: I once had a compile fail on Motorola's MPL compiler, which was
> written in fortran. It had so many continued comment lines that the 16-bit
> column number went negative, and I got a fairly obscure error.
>
>
>
> Anyone remember who wrote it?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170307/a60850d7/attachment.html>


  reply	other threads:[~2017-03-07 19:53 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 [this message]
2017-03-07 20:03       ` Paul Ruizendaal
2017-03-07 21:05       ` Clem Cole
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=CAEoi9W5Pa1jG45YoZ-VsSGbPB36EHrMEUX71hXq-Lm52nt253A@mail.gmail.com \
    --to=crossd@gmail.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).