The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] lost ports
Date: Thu, 5 Jan 2017 11:20:02 -0500	[thread overview]
Message-ID: <CAC20D2M-+8Rfzr0FHUtmqiTT4pvMXFmdUnhUNG+BWFpc3v6cdw@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2P6qxW24Hv_cU-ctpzehEWZhNWHQ7O6uTvgbup+fiViSA@mail.gmail.com>

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

​I also left out....

E.) GEM tools ran on VMS, Ultrix, Mica, OSF/1, Tru64, Mac OSx, NT/4 and
later Windows version up too and now Win10​

And I was just reminded that there was a 68K back-end done for it also that
terminal folks used, although I'm not sure I ever saw it.

Ron - for whatever its worth, the whole BLISS vs C is different history
both outside and inside of DEC [which some of lived and I'll not repeat it
here].   But it is sadly miss represented.   I'm a C programmer and while I
learned BLISS before C, I certainly prefer C to BLISS as do many of my
peers - even heavy, heavy BLISS hackers I know.

You should know that the compiler team was definitely BLISS based, as was
the VMS group, but once Streams I/O was added to VMS and the C compiler
introduced, most VMS customers left RMS I/O; while continuing to use
FORTRAN as the primary VMS end-user language, BLISS was less so, C and
Pascal quickly became more popular.   Even at DEC, C took off, particularly
in the HW teams if for no other reason than you could hire C programmers
from Universities and you had to teach them BLISS.

Clem

On Thu, Jan 5, 2017 at 11:01 AM, Clem Cole <clemc at ccc.com> wrote:

> ​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/1b29c68f/attachment.html>


  reply	other threads:[~2017-01-05 16:20 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
2017-01-05 16:20   ` Clem Cole [this message]
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=CAC20D2M-+8Rfzr0FHUtmqiTT4pvMXFmdUnhUNG+BWFpc3v6cdw@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).