Re: g77 (was *.f *.c linking problem)

["Dr H. T. Leung" <htl10 at cus dot cam dot ac dot uk>]

So you are saying that gcc 2.8.1 <> egcs 1.0.3a, and g77 0.5.23 is a later
package; and the next update in the gcc/g77 scenerio is egcs 1.1 which
will come out in about a month's time? 

I think the development effort should be more co-ordinated - besides it
being duplicating efforts, it is a terrible mess to have to cope with
three version of libf2c (GNU's egcs', and netlib's) and two versions of
gcc and g77; okay, netlib's is less of a problem because I put them into a
different directory, and only do an explicit -L there (if I have to); but
the gcc/g77 stuff goes with the system and they actually over-write each
other (at least the binary). 

Can we make them function more similarly to the proprietary Sun compilers
(or others)? I think the Sun f77 compiler wouldn't moan if you compile c
codes with it... Not sure whether this is a "correct" practice, but there
are strange people out there who write fortran codes then a C wrapper,
etc. Porting these codes are difficult.

I will wait for the next egcs...

On Tue, 14 Jul 1998, Craig Burley wrote:

> gcc 2.8.1 came out around the same time as egcs 1.0.3a (or 1.0.2) or
> so, so those two have roughly the same bug fixes.  (They're not
> identical, though; sometimes one has an optimization that another
> doesn't have, which can also mean it has, or exposes, bugs the
> other doesn't.)
> 
> However, g77 0.5.23 is the most recent released version of g77 and
> the corresponding libf2c, while egcs 1.0.3a included basically a
> variant of g77 0.5.22.
> 
> The official FSF version of g77 and the egcs version will probably
> do a bit of leapfrogging due to different release schedules, although
> right now I'm working on reducing the differences, which might mean
> FSF-g77 gets released right around the same time as any new egcs
> (assuming the latter has g77 changes).  0.5.23 "made up" for a huge
> existing problem, namely, that no non-egcs version of g77 existed
> that operated on the gcc 2.8 backend (which is what egcs 1.0 started
> with, basically), but it also included some changes that have yet to
> appear in a released version of egcs.
> 
> However, egcs *snapshots* (and the CVS source tree) have generally had
> the latest g77 improvements within a week or two, though with the
> 0.5.23 changes there was a longer delay because there were so many
> of them.
> 
> Since the g77 version you get includes both g77 and libf2c, that's
> mostly what you'll notice in terms of which new fatures and such that
> it has.
> 
> egcs 1.1 is now in "bug-fix-only" mode, and should be released soon.
> (See <http://www.cygnus.com/egcs>, I assume.)  If you can't wait,
> try g77 0.5.23.  At least you could experiment with 0.5.23 to get
> your code prepared for egcs 1.1.
> 
>         tq vm, (burley)