This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA] Generalizing compiler invocation for FORTRAN95 testsuite
- From: Michael Elizabeth Chastain <mec at shout dot net>
- To: petrs at caldera dot com
- Cc: gdb-patches at sources dot redhat dot com
- Date: Wed, 8 May 2002 22:19:22 -0500
- Subject: Re: [RFA] Generalizing compiler invocation for FORTRAN95 testsuite
Okay, progress report.
I'm playing around with some new code in gdb_compile() to set the compiler
name. It looks in the arguments to see if there is a language argument
such as "c++" or "fortran-90". If there is a language argument, that's
the language to use. If there is no language argument, the default
language is C.
Next there is a section that translates the language argument to a compiler
to use. That's where the default compilers are gcc, g77, gjc, and so on.
The user can override these with environment variables CC_FOR_TARGET,
F77_FOR_TARGET, JAVA_FOR_TARGET, and so on. This will enable people to
test with different C compilers and different C++ compilers and
different FORTRAN compilers.
After gdb_compile() figures out the name of the compiler, it always
passes a "compiler=..." argument to target_compile.
Along the way, I ripped out a lot of weird lib/java.exp support code to
figure out the name of the Java compiler.
I'm still playing with this. Among other things, I have to fix my own
Java testbed problems first so that I can run Java tests.
When it reaches a submission stage I'll be happy to have it stomped on
and ripped up; I'm not assuming that anyone will like it.
Michael C