From: Andrew Cagney <cagney@gnu.org>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFA] PR gdb/648 (eval.c approval reqd)
Date: Fri, 27 Aug 2004 15:57:00 -0000 [thread overview]
Message-ID: <412F599C.3060902@gnu.org> (raw)
In-Reply-To: <412F4BD3.nailEEQ135PPF@mindspring.com>
I can see your point, and it's valid.
I was thinking of a very simple procedure:
proc deprecated_compile_with_gnu_fortran { program } { .... }
and have the fortran tests use that.
Attatched to the procedure would be a comment stating that anyone
wanting to modify the testsuite to support non-GNU fortran will need to
implement the infrastructure you describe described.
That way the fortran test directory can be populated with tests
simultaneous to, or even prior to, adding the feature. While at the
same time, establishing a very clear acceptance criteria for anyone
wanting to hack things for non-GNU compilers.
how does this sound?
Andrew
next prev parent reply other threads:[~2004-08-27 15:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-06 22:10 [PATCH/RFA] PR gdb/648 David Lecomber
2004-08-13 10:25 ` David Lecomber
2004-08-13 10:32 ` Michael Chastain
2004-08-13 22:14 ` Jim Blandy
2004-08-16 12:33 ` David Lecomber
2004-08-16 12:38 ` David Lecomber
2004-08-18 16:36 ` Jim Blandy
2004-08-20 13:37 ` [PATCH/RFA] PR gdb/648 (eval.c approval reqd) David Lecomber
2004-08-20 13:45 ` David Lecomber
2004-08-25 5:53 ` Jim Blandy
2004-08-25 7:24 ` David Lecomber
2004-08-27 0:00 ` Jim Blandy
2004-08-27 9:15 ` David Lecomber
2004-08-27 13:52 ` Andrew Cagney
2004-08-27 13:58 ` Michael Chastain
2004-08-27 14:14 ` Andrew Cagney
2004-08-27 14:57 ` Michael Chastain
2004-08-27 15:57 ` Andrew Cagney [this message]
2004-08-27 16:15 ` Michael Chastain
2004-08-30 14:17 ` Andrew Cagney
2004-08-23 19:26 ` [PATCH/RFA] PR gdb/648 Andrew Cagney
2004-08-24 18:03 ` Jim Blandy
2004-08-15 8:19 ` Michael 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=412F599C.3060902@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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