From: Warner Losh <imp@bsdimp.com>
To: Paul Winalski <paul.winalski@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] DEC compilers (was Happy birthday, John Backus!)
Date: Wed, 5 Dec 2018 10:06:15 -0700 [thread overview]
Message-ID: <CANCZdfo41Oiii1Urfhc+5KTJzgW6cAiEXyjCzaXVeE7TM7=Enw@mail.gmail.com> (raw)
In-Reply-To: <CABH=_VSr8tByoz8FOoGpe6Yz8CH_Zbi10qOLMb15eX-+oBhB+w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
On Wed, Dec 5, 2018 at 9:48 AM Paul Winalski <paul.winalski@gmail.com>
wrote:
> Another curious compiler at DEC was VAX Ultrix Fortran. DEC had
> gotten a lot of push-back from the research community, who wanted to
> use VAX and Ultrix but considered the f77 compiler inadequate and
> wanted to use VAX Fortran, which only ran on VAX/VMS. There was a
> rush project to port VAX Fortran to Ultrix. It was decided that the
> quickest way to get a quality compiler to market was to have the VAX
> Fortran compiler continue to emit VMS-format object files, and to
> modify the VAX/VMS linker to accept a.out object files and to emit
> a.out images. Four of us worked on the linker port. Two of us from
> the VAX/VMS languages team did the linker mods and two engineers from
> the Ultrix group wrote code to translate VMS debug information to Unix
> stabs. The resulting linker was called lk. The VAX Fortran RTL was
> also ported, and since we had a way to produce Unix executables from
> VMS object files, it meant we didn't have to rewrite the RTL, which
> was mainly in BLISS but also had modules in Fortran, VAX assembler,
> and Pascal.
>
Nice work! We ran VMS on our MicroVAX rather than Ultrix or 4.[23]BSD
because of the FORTRAN compiler being so much better on VMS and our group
needing it for its hydrological simulations.
Warner
[-- Attachment #2: Type: text/html, Size: 1701 bytes --]
next prev parent reply other threads:[~2018-12-05 17:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 16:24 Paul Winalski
2018-12-05 16:46 ` Paul Winalski
2018-12-05 17:06 ` Warner Losh [this message]
2018-12-05 17:58 ` Clem Cole
2018-12-05 18:16 ` Paul Winalski
2018-12-05 18:26 ` Henry Bent
2018-12-05 18:46 ` Clem Cole
2018-12-05 18:56 ` Lars Brinkhoff
2018-12-05 19:15 ` Paul Winalski
2018-12-05 21:35 ` Arrigo Triulzi
2018-12-07 19:03 ` Paul Winalski
2018-12-05 19:13 Norman Wilson
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='CANCZdfo41Oiii1Urfhc+5KTJzgW6cAiEXyjCzaXVeE7TM7=Enw@mail.gmail.com' \
--to=imp@bsdimp.com \
--cc=paul.winalski@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).