Path: utzoo!news-server.csri.toronto.edu!rpi!usc!elroy.jpl.nasa.gov!decwrl!pa.dec.com!rust.zso.dec.com!shlump.nac.dec.com!riscy.enet.dec.com!croton.nyo.dec.com!frank
From: frank@croton.nyo.dec.com (Frank Wortner)
Newsgroups: comp.unix.ultrix
Subject: Re: New RISC compilers????
Message-ID: <1972@riscy.enet.dec.com>
Date: 18 Mar 91 14:45:15 GMT
References: <3276@canisius.UUCP> <15530012@hpdmd48.boi.hp.com>
Sender: newsdaemon@riscy.enet.dec.com
Reply-To: frank@croton.nyo.dec.com (Frank Wortner)
Organization: Digital Equipment Corporation
Lines: 31

In article <3276@canisius.UUCP>, pavlov@canisius.UUCP (Greg Pavlov) writes:
>   They're homebrews.  We purchased the VAX processor-based FORTRAN compiler
>   when that came out, to get the extra "speed", courtesy of the VMS folks,
>   I believe.
> 

The compilers are written a separate software group that develops tools for
all Digital platforms.  While they do create products for the VAX/VMS operating
system, they don't write the OS, and they aren't the "VMS folks."

>   While it may be unfair to say this (another processor, after all), the
>   resulting experiences led me to adopt a "the extra SPECS ain't
>   worth it" motto.  Lots of bugs, very slow fixes, and some rather arcane
>   suggested workarounds (compile the errant routines in f77 and connect
>   via the infamous "jacket" routines, for instance...).
>

The new DEC Fortran compiler is a *brand new* product.  It is not just VAX/VMS
Fortran ported to RISC.  Please don't pre-judge this compiler without actually
using it.  It has gone through a lengthy field test with the idea of
shaking out
as many bugs as possible.

BTW,  this compiler *does not* use Jacket Building Language.  It has the same
calling conventions as the current f77 compiler.

While I'm hardly an unbiased observer  ;-), I've used both this compiler and
a couple of others during the past few months.  Personally, I don't think we
have to take a back seat to anyone.

					Frank