Patch: f2c.h Question: objc backend

[Alexandre Oliva]

Craig Burley writes:

> So, to make this version of `f2c.h' available to users of f2c
> on the system, g77 installs it, along with the version of `libf2c.a'
> it built, in the canonical include and lib directories if `libf2c.a'
> isn't already there or explicit overriding macros and/or files
> exist in the build or source directories.

I believe this is unnecessary, since, if people compile C files
(translated from Fortran by f2c) with gcc, it will find f2c.h anyway,
and it will link against g77's libf2c.a.  Is my reasoning wrong?

>   1.  We could bring all of f2c into the gcc/g77 product packaging.

Is there any reason to make f2c available?  I can't think of any
reason to use it, since there is g77, which makes such a better job
about optimizing loops and such, AFAIK.

>   2.  We could start to drop any semblance of f2c compatibility from
>       g77

Could there be any performance gain with that?

-- 
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil