This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
gfortran.dg testsuite patch (committed)
- From: "Billinghurst, David (CALCRTS)" <david dot billinghurst at comalco dot riotinto dot com dot au>
- To: <gcc-patches at gcc dot gnu dot org>
- Cc: <fortran at gcc dot gnu dot org>,<tobias dot schlueter at physik dot uni-muenchen dot de>
- Date: Sat, 10 Jul 2004 00:43:37 +1000
- Subject: gfortran.dg testsuite patch (committed)
This "obvious" tweak fixes the regexp in the gfortran.dg driver
that collapses the gfortran error|warning messages to a single
line. It may need further tweaks as we add more tests.
I have also copied across a g77 test to show that it works.
It now "works for me". I will now let the testsuite settle while
we shake out any problems from other platforms.
Tobi - see how you go with your tests. Let me know if I can
help.
2004-07-10 David Billinghurst (David.Billinghurst@riotinto.com)
* lib/gfortran-dg.exp (gfortran-dg-test): Adapt regular
expression to match gfortran warning/error messages
* gfortran.dg/g77/12632.f: Copy from g77.dg and fix
dg-error text.
Index: gfortran-dg.exp
===================================================================
RCS file: /cvs/gcc/gcc/gcc/testsuite/lib/gfortran-dg.exp,v
retrieving revision 1.1
diff -u -r1.1 gfortran-dg.exp
--- gfortran-dg.exp 8 Jul 2004 23:12:47 -0000 1.1
+++ gfortran-dg.exp 9 Jul 2004 14:16:07 -0000
@@ -26,9 +26,10 @@
set output_file [lindex $result 1]
# Put the error message on the same line as the line number
+ # FIXME: Add a colon after line number
# Remove the line of source code with the error and
- # the " ^" that points to error
- regsub -all "\n\[^\n\]*\n *\\^\n" $comp_output "" comp_output
+ # the number pointing to error
+ regsub -all "\n\n\[^\n\]*\n *\[0-9\]*\n" $comp_output ": " comp_output
return [list $comp_output $output_file]
}