This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libf2c cross-compile doesn't
- To: rth at cygnus dot com (Richard Henderson)
- Subject: Re: libf2c cross-compile doesn't
- From: cgd at sibyte dot com (Chris G. Demetriou)
- Date: 01 May 2000 10:02:23 -0700
- Cc: gcc-bugs at gcc dot gnu dot org
- References: <871z3ukmsm.fsf@mail.netbsd.org> <20000428180813.A14191@cygnus.com> <mailpost.956970513.8161@baton.sibyte.com>
rth@cygnus.com (Richard Henderson) writes:
> On Tue, Apr 25, 2000 at 12:23:05PM -0700, Chris G. Demetriou wrote:
> > checking f2c integer type... configure: error: Can't run check for
> > integer sizes -- see config.log
>
> Yes. This is a fundamental problem with libg2c.
Thinking about it more, I'd also think that in addition to the basic
cross-compile case that i mentioned, it'd also cause problems when
GCC's types can be changed by use of target_flags...
> IMO this should be handled not by having libf2c poke gcc/f/
> internals, but rather to have a __g77_integer type built in
> to the C front end. This is similar to e.g. __java_byte in
> the C++ front end for Java runtime support.
Well, it's not clear to me that either of those are particularly
pretty. (it seems that it's ... less than desirable to put info about
one language's library into the front-end of another, eh?)
I guess i'll give it a go, but I may get it totally wrong. (I've
never hacked on gcc before. 8-)