🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.arch
Article #2517

Re: VLIW Architecture

#2517
From: Martin E. Lewitt
Date: Tue, 10 Oct 1989 10:08
33 lines
2299 bytes
In article <13109@pur-ee.UUCP> hankd@pur-ee.UUCP (Hank Dietz) writes:
= In article <1071@m3.mfci.UUCP> colwell@mfci.UUCP (Robert Colwell) writes:
= >In article <3449@alliant.Alliant.COM> lewitt@Alliant.COM (Martin Lewitt) writes:
= >>       3) The first commercially available machine to compile complete
= >>          HLL applications to micro-code was once again, the FPS-164
= 
= Were "complete HLL applications" really compiled to microcode?  I thought
= they ran partly on the host machine?

The FPS-164 and its successors almost always ran complete applications, the
"subroutine box" mode was not used by most customers.  This was made possible
by an advanced (for FPS) OS called the Single Job Executive (SJE).

= >>       4) The first commercially available machine to successfully exploit 
= >>          parallel processors automatically using "dusty deck", serial 
=             ^^^^^^^^
= >>          FORTRAN, the Alliant FX8, (by 4 years and counting).
= >
= >"And counting"?  What does that mean?
= 
= Are you defining "parallel" to be MIMD, but not SIMD/Vector?  In either
= case, doesn't Cray count?  I don't know what compilers have been marketed,
= but I know of more than a few "dusty deck" compilers for MIMD targets....

I was thinking MIMD.  Until recently didn't Cray MIMD require
micro-tasking directives inserted in the code on the based on user analysis
of the code?

= 						-hankd@ecn.purdue.edu
-- 
Phone: (206) 931-8364			Martin E. Lewitt      My opinions are
Domain: lewitt@alliant.COM		2945 Scenic Dr. SE    my own, not my
UUCP: {linus|mit-eddie}!alliant!lewitt  Auburn, WA 98002      employer's. 
Technical Details
Message-ID: <3459@alliant.Alliant.COM>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!bloom-beacon!spdcc!merk!alliant!lewitt
References: <251FCB3F.12366@maccs.dcss.mcmaster.ca> <1050@m3.mfci.UUCP> <13050@pur-ee.UUCP> <1630@l.cc.purdue.edu> <1989Oct5.025841.2046@esegue.segue.boston.ma.us> <3449@alliant.Alliant.COM> <1071@m3.mfci.UUCP> <13109@pur-ee.UUCP>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!bloom-beacon!spdcc!merk!alliant!lewitt
From: lewitt@Alliant.COM (Martin E. Lewitt)
Newsgroups: comp.arch
Subject: Re: VLIW Architecture
Keywords: VLIW
Message-ID: <3459@alliant.Alliant.COM>
Date: 10 Oct 89 10:08:14 GMT
References: <251FCB3F.12366@maccs.dcss.mcmaster.ca> <1050@m3.mfci.UUCP> <13050@pur-ee.UUCP> <1630@l.cc.purdue.edu> <1989Oct5.025841.2046@esegue.segue.boston.ma.us> <3449@alliant.Alliant.COM> <1071@m3.mfci.UUCP> <13109@pur-ee.UUCP>
Reply-To: lewitt@alliant.Alliant.COM (Martin E. Lewitt)
Organization: Alliant Computer Systems, Littleton, MA
Lines: 33