[Info-vax] GCC for VMS, was: Re: fortran compiler roadmap?

[Bill Gunshannon]

In article <nospam-AC92AF.16315818042013 at news.chingola.ch>,
	Paul Sture <nospam at sture.ch> writes:
> In article 
> <craigberry-0E8D50.22030917042013 at news.eternal-september.org>,
>  "Craig A. Berry" <craigberry at mac.com.invalid> wrote:
> 
>> While VAX Fortran was my first computer language, I haven't done any 
>> Fortran in twenty years and I don't have a very good sense of what role 
>> the library plays in the language.  Given that SYS$SHARE:DEC$FORRTL.EXE 
>> is about one tenth the size of SYS$SHARE:DECC$SHR.EXE, I'm guessing 
>> it's not quite as big a deal as the C run-time.  But still, getting a 
>> "foreign" Fortran compiler fully functional on VMS would likely require 
>> various kinds of glue for exit handlers, threads, and such, and, if you 
>> want to use native libraries, rights to use SYS$LIBRARY:FORSYSDEF.TLB 
>> or an independently-developed equivalent.
> 
> Going back to the last time I used VAX Fortran we made extensive use of 
> third party libraries and runtime processes.  

NAGLIB, by any chance?

>                                               I believe those did make 
> it to Alpha, but don't know whether they made it to Itanium.  Without 
> those a complete rewrite of the applications would be the only way 
> forwards.

Is NAGLIB still around?  We always got it in source (Fortran) so I
guess it could be used on any system with a functional Fortran Compiler.

bill


-- 
Bill Gunshannon          |  de-moc-ra-cy (di mok' ra see) n.  Three wolves
billg999 at cs.scranton.edu |  and a sheep voting on what's for dinner.
University of Scranton   |
Scranton, Pennsylvania   |         #include <std.disclaimer.h>