Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: "gdb-patches@sources.redhat.com" <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] Generalizing compiler invocation for FORTRAN95 testsuite
Date: Tue, 07 May 2002 09:18:00 -0000	[thread overview]
Message-ID: <20020507161840.GA20239@nevyn.them.org> (raw)
In-Reply-To: <3CD7EDA7.111E6F4B@caldera.com>

On Tue, May 07, 2002 at 11:07:19AM -0400, Petr Sorfa wrote:
B> Hi,
> 
> I'm going to be releasing the FORTRAN95 testsuite soon. Unfortunately
> since there is currently no functional g95 the testsuite relies on
> invoking Intel's FORTRAN95 compilers (efc (IA64) and ifc (IA32).)
> 
> I'm just wondering how I should generalize this dependency and still
> invoke the correct compilers?

I recommend putting this logic directly into DejaGNU.  You might want
to ask on the DejaGNU list about how best to do it; Rob has a lot of
experience with this sort of magic.

> Would it also be a good idea to create a gdb.fortran95 directory under
> gdb/testsuite/?

Probably.

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-05-07 16:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-07  7:55 Petr Sorfa
2002-05-07  9:18 ` Daniel Jacobowitz [this message]
2002-05-07  9:27 ` Eli Zaretskii
2002-05-07  9:30   ` Petr Sorfa
2002-05-07  8:59 Michael Elizabeth Chastain
2002-05-07  9:04 ` Petr Sorfa
2002-05-07  9:20 Michael Elizabeth Chastain
2002-05-08 20:19 Michael Elizabeth Chastain
2002-05-10 11:07 ` Petr Sorfa
2002-05-10 11:25 Michael Elizabeth Chastain
2002-05-10 11:38 ` Andrew Cagney
2002-05-10 12:19 Michael Elizabeth Chastain

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020507161840.GA20239@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox