From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21305 invoked by alias); 10 May 2002 18:07:29 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 21296 invoked from network); 10 May 2002 18:07:26 -0000 Received: from unknown (HELO tetsuo.nj.caldera.com) (63.124.204.226) by sources.redhat.com with SMTP; 10 May 2002 18:07:26 -0000 Received: from caldera.com (localhost.localdomain [127.0.0.1]) by tetsuo.nj.caldera.com (8.11.6/8.11.6) with ESMTP id g4AIJWc06982; Fri, 10 May 2002 14:19:33 -0400 Message-ID: <3CDC0F34.E9C676D1@caldera.com> Date: Fri, 10 May 2002 11:07:00 -0000 From: Petr Sorfa Organization: Caldera X-Accept-Language: en MIME-Version: 1.0 To: Michael Elizabeth Chastain CC: gdb-patches@sources.redhat.com Subject: Re: [RFA] Generalizing compiler invocation for FORTRAN95 testsuite References: <200205090319.g493JMC19527@duracef.shout.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-05/txt/msg00349.txt.bz2 Hi Michael, Sounds good. Should I keep my current compiler support in the F95 testsuite or change it temporarily until your work becomes available? Petr > 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