The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Luther Johnson <luther.johnson@makerlisp.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Multiflow Compiler
Date: Mon, 1 Apr 2024 12:12:27 -0700	[thread overview]
Message-ID: <4a466a5a-38cc-9ddc-bcbd-1fb781bf6ab7@makerlisp.com> (raw)
In-Reply-To: <202404011853.431Irt2E880190@darkstar.fourwinds.com>

You can always read Josh Fisher's book on the "Bulldog" compiler, I
believe he did this work at Yale.

On 04/01/2024 11:53 AM, Jon Steinhart wrote:
> Henry Bent writes:
>> I happened upon
>> https://old.gustavobarbieri.com.br/trabalhos-universidade/mc722/lowney92multiflow.pdf
>> and I am curious as to whether any of the original Multiflow compilers
>> survive.  I had never heard of them before now, but the fact that they were
>> licensed to so many influential companies makes me think that there might
>> be folks on this list who know of its history.
>>
>> -Henry
> Great question.  Unfortunately, Cindy passed away last summer.
> I haven't been in touch with John or Ben in decades and don't
> know how to reach them.  They used to have a company called
> Equator (I think) that continued work on their trace scheduling
> compilier after the demise of Multiflow.  I do have a big file
> folder with info on the compiler design but I don't think that
> I'm free to share it.
>
> Jon
>


  reply	other threads:[~2024-04-01 19:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01 18:44 [TUHS] " Henry Bent
2024-04-01 18:53 ` [TUHS] " Jon Steinhart
2024-04-01 19:12   ` Luther Johnson [this message]
2024-04-02  3:46 ` Lawrence Stewart
2024-04-02 15:53 ` Paul Winalski
2024-04-02 16:37   ` Paul Winalski
     [not found] <171209236009.1214089.9696983396368447310@minnie.tuhs.org>
2024-04-02 22:55 ` Paul McJones
2024-04-02 23:46   ` Luther Johnson

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=4a466a5a-38cc-9ddc-bcbd-1fb781bf6ab7@makerlisp.com \
    --to=luther.johnson@makerlisp.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).