Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Chastain <mec.gnu@mindspring.com>
To: gdb-patches@sources.redhat.com
Subject: [rfc/testsuite/fortran] add fortran programs
Date: Sun, 15 Aug 2004 08:39:00 -0000	[thread overview]
Message-ID: <411F2121.nailA3X1XNYD7@mindspring.com> (raw)

Hey, gdb.fortran has no actual FORTRAN programs in it!
I'm going to fix that.

My plan is:

  (1A) Add gdb.fortran/Makefile.in.  The test subdirectories have
       trivial Makefile.in files that don't do much, but it's actually
       necessary to have one of these and hook it up to configure
       and configure.in so that $build/testsuite/gdb.fortran gets
       created.
  (1B) Add skip_fortran_tests to lib/gdb.exp.

  (2)  Add a simple "hello world" test.  The very first test is
       going to KFAIL, because the gdb command "start" does not work
       with FORTRAN!

  (3)  Shake that out for several days.

  (4)  Add a test script for gdb/648, from David Lecomber's work.

dejagnu 1.4.4 is set up so that language "f77" runs a compiler named
"g77".  If "g77" is not available on some targets, then we can add those
targets to "skip_fortran_tests".  Look at testsuite/lib/gdb.exp
procedure "skip_cplus_tests" for the idea.

Here is the patch for (1A) and (1B).  I haven't tested this yet.

I'll give this plan 48 hours for comments, then commit the first
patch.  Note: "yo, I'm really busy but I want to talk about this
before you charge into the implementation" is a perfectly valid
comment.

Michael C

2004-08-15  Michael Chastain  <mec.gnu@mindspring.com>

	* configure.in: Add gdb.fortran.
	* configure: Regenerate.
	* gdb.fortran/Makefile.in: New file.
	* lib/gdb.exp (skip_fortran_tests): New procedure.

Index: configure.in
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/configure.in,v
retrieving revision 1.15
diff -c -3 -p -r1.15 configure.in
*** configure.in	20 Jul 2004 23:11:21 -0000	1.15
--- configure.in	15 Aug 2004 08:13:53 -0000
*************** AC_CONFIG_SUBDIRS($configdirs)
*** 121,125 ****
  AC_OUTPUT([Makefile \
    gdb.ada/Makefile gdb.ada/gnat_ada.gpr:gdb.ada/gnat_ada.gin \
    gdb.arch/Makefile gdb.asm/Makefile gdb.base/Makefile \
!   gdb.cp/Makefile gdb.disasm/Makefile gdb.java/Makefile gdb.mi/Makefile \
    gdb.objc/Makefile gdb.threads/Makefile gdb.trace/Makefile])
--- 121,126 ----
  AC_OUTPUT([Makefile \
    gdb.ada/Makefile gdb.ada/gnat_ada.gpr:gdb.ada/gnat_ada.gin \
    gdb.arch/Makefile gdb.asm/Makefile gdb.base/Makefile \
!   gdb.cp/Makefile gdb.disasm/Makefile gdb.fortran/Makefile \
!   gdb.java/Makefile gdb.mi/Makefile \
    gdb.objc/Makefile gdb.threads/Makefile gdb.trace/Makefile])
Index: lib/gdb.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/lib/gdb.exp,v
retrieving revision 1.54
diff -c -3 -p -r1.54 gdb.exp
*** lib/gdb.exp	9 Aug 2004 13:16:15 -0000	1.54
--- lib/gdb.exp	15 Aug 2004 08:14:03 -0000
*************** proc skip_cplus_tests {} {
*** 1121,1126 ****
--- 1121,1132 ----
      return 0
  }
  
+ # Return a 1 if I don't even want to try to test FORTRAN.
+ 
+ proc skip_fortran_tests {} {
+     return 0
+ }
+ 
  # Skip all the tests in the file if you are not on an hppa running
  # hpux target.
  
=== gdb.fortran/Makefile.in

# Makefile for regression testing the GNU debugger.
# Copyright 1992, 1993, 1994, 1995, 1996, 1999, 2001, 2003, 2004
# Free Software Foundation, Inc.

# This file is part of GDB.

# GDB is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2, or (at your option)
# any later version.

# GDB is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.

# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.

VPATH = @srcdir@
srcdir = @srcdir@

EXECUTABLES = 

all info install-info dvi install uninstall installcheck check:
	@echo "Nothing to be done for $@..."

clean mostlyclean:
	-rm -f *~ *.o *.ci
	-rm -f core ${EXECUTABLES}

distclean maintainer-clean realclean: clean
	-rm -f Makefile config.status config.log


             reply	other threads:[~2004-08-15  8:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-15  8:39 Michael Chastain [this message]
2004-08-17 16:41 ` 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=411F2121.nailA3X1XNYD7@mindspring.com \
    --to=mec.gnu@mindspring.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