From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] lost ports
Date: Thu, 5 Jan 2017 11:01:49 -0500 [thread overview]
Message-ID: <CAC20D2P6qxW24Hv_cU-ctpzehEWZhNWHQ7O6uTvgbup+fiViSA@mail.gmail.com> (raw)
In-Reply-To: <CAP6exYLat4Xucfj7V99Ev8SeA8jV3NDA7axia6Ta=k+mr62Kiw@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1510 bytes --]
below...
On Wed, Jan 4, 2017 at 4:24 PM, ron minnich <rminnich at gmail.com> wrote:
> but another true story: I visited DEC in 2000 or so, as LANL was about to
> spend about $120M on an Alpha system. The question came up about the SRM
> firmware for Alpha. As it was described to me, it was written in BLISS and
> the only machine left that could build it was an 11/750, "somewhere in the
> basement, man, we haven't turned that thing on in years". I suspect there's
> a lot of these containing oxide oersteds of interest.
Cute story but not true [and I was @ DEC working Alpha at that time].
Some facts:
A.) The SRM firmware was in C primary and Assembler and used >>UNIX<< tools
not VMS tools for development
B.) The GEM compiler (which still exists and still being developed by VMSI)
had front ends for at least (which I remember): BLISS, C, PL/1, Pascal,
ADA, FORTRAN, Cobol, RPG and a few others (I'll try to ask if I see any of
the old GEM guys in the Cafe' in the next few hours - they are dying off
BTW - but that's a different story).
C.) The GEM compiler has backends for, Vax, Galaxy, MIPS, Alpha, x86
(32bit), ia64, INTEL*64 (post DEC/Compaq/HP) and I believe also ARM (I'll
need to ask if the VMSI folks come to lunch on Friday).
D.) Alpha's ran UNIX before they ran VMS BTW. The HW debug was all UNIX.
Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170105/44c8f775/attachment.html>
next prev parent reply other threads:[~2017-01-05 16:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 21:24 ron minnich
2017-01-04 21:41 ` Ron Natalie
2017-01-04 21:58 ` Larry McVoy
2017-01-05 1:52 ` Larry McVoy
2017-01-04 22:01 ` Robert Swierczek
2017-01-04 22:01 ` Dan Cross
2017-01-05 16:01 ` Clem Cole [this message]
2017-01-05 16:20 ` Clem Cole
2017-01-05 17:23 ` ron minnich
2017-01-05 19:08 ` Clem Cole
2017-01-05 19:16 ` ron minnich
2017-01-05 20:08 ` Clem Cole
[not found] ` <E3DA30C5-7227-4143-8DA1-401A161C74C6@gmail.com>
[not found] ` <CAP6exYLvXvtGEWSg_t5bqjJwunGKC1xiiaoLj7yb5QxkHsMvuA@mail.gmail.com>
2017-01-05 23:40 ` Lawrence Stewart
2017-01-05 16:15 ` Derek Fawcus
2017-01-05 18:34 ` Pierre DAVID
2017-01-05 12:28 Rudi Blom
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=CAC20D2P6qxW24Hv_cU-ctpzehEWZhNWHQ7O6uTvgbup+fiViSA@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).