Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!ncar!csn!boulder!news!grunwald
From: grunwald@foobar.colorado.edu (Dirk Grunwald)
Newsgroups: comp.unix.ultrix
Subject: Re: Fortran weirdnesses
Message-ID: <1991May2.044132.27928@colorado.edu>
Date: 2 May 91 04:41:32 GMT
References: <HUDGENS.91Apr29142057@sun13.sun13.SCRI.FSU.EDU>
	<1991May1.220455.11441@fys.ruu.nl>
Sender: news@colorado.edu (The Daily Planet)
Reply-To: grunwald@foobar.colorado.edu
Organization: University of Colorado at Boulder
Lines: 13
In-Reply-To: mos@fys.ruu.nl's message of 1 May 91 22:04:55 GMT
Nntp-Posting-Host: foobar.colorado.edu


Is anyone at DEC at liberty to say if the RISC OSF/1 based offering
will still use the icky MIPS ECOFF object file format, or will they be
switching to ROSE, or will there be a choice (i.e. different kernel
loaders) or what.

Given that the Gnu C compiler V2beta produces code as good as the mips
compiler (unless you enable -O4), it would be nice to be able to move
away from the crufty MIPS object file format, because it causes no end
of problem when you attempt to use e.g., G++ on these beasties.

Thanks. I don't think anyone will be able to say, but what the hey,
why not try.