[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs and GFortran
From: |
Brooks Moses |
Subject: |
Re: Emacs and GFortran |
Date: |
Thu, 02 Nov 2006 18:32:55 -0800 |
User-agent: |
Mozilla Thunderbird 1.0.2 (Windows/20050317) |
Steve Kargl wrote:
I have stated more than once THE TRIVIAL FIX DOES NOT WORK.
It causes REGRESSIONS in the gfortran testsuite. If someone
wants to fix whatever is causing the regressions, I'll be more
than happy to commit the patch.
The attached only-slightly-less-trivial patch should fix the
regressions, although I have not yet tested it to confirm that.
Since my build machine is currently occupied with running CFD
calculations for my dissertation, would you mind regtesting it?
- Brooks
Index: testsuite/lib/gfortran-dg.exp
===================================================================
--- testsuite/lib/gfortran-dg.exp (revision 118446)
+++ testsuite/lib/gfortran-dg.exp (working copy)
@@ -26,23 +26,23 @@
set output_file [lindex $result 1]
# gfortran error messages look like this:
- # In file [name]:[line]
+ # [name]:[line]
#
# some code
# 1
- # Error: Some error at (1) and (2)
+ # Error: Some error at (1)
# or
- # In file [name]:[line]
+ # [name]:[line]
#
# some code
# 1
- # In file [name]:[line2]
+ # [name]:[line2]
#
# some other code
# 2
# Error: Some error at (1) and (2)
# or
- # In file [name]:[line]
+ # [name]:[line]
#
# some code and some more code
# 1 2
@@ -59,7 +59,7 @@
# Note that these regexps only make sense in the combinations used below.
# Note also that is imperative that we first deal with the form with
# two loci.
- set locus_regexp " In file (\[^\n\]*)\n\n\[^\n\]*\n\[^\n\]*\n"
+ set locus_regexp " (\[^\n\]*)\n\n\[^\n\]*\n\[^\n\]*\n"
set diag_regexp "(\[^\n\]*)\n"
set two_loci "$locus_regexp$locus_regexp$diag_regexp"
Index: fortran/error.c
===================================================================
--- fortran/error.c (revision 118446)
+++ fortran/error.c (working copy)
@@ -134,7 +134,7 @@
lb = loc->lb;
f = lb->file;
- error_printf ("In file %s:%d\n", f->filename,
+ error_printf ("%s:%d\n", f->filename,
#ifdef USE_MAPPED_LOCATION
LOCATION_LINE (lb->location)
#else
- Re: Emacs and GFortran, (continued)
- Re: Emacs and GFortran, Thomas Koenig, 2006/11/03
- Re: Emacs and GFortran, Steve Kargl, 2006/11/03
- Re: Emacs and GFortran, Eli Zaretskii, 2006/11/03
- Re: Emacs and GFortran, David Kastrup, 2006/11/03
- Re: Emacs and GFortran, Eli Zaretskii, 2006/11/03
- Re: Re: Emacs and GFortran, François-Xavier Coudert, 2006/11/03
- Re: Emacs and GFortran, Eli Zaretskii, 2006/11/03
- Re: Emacs and GFortran, Steven Bosscher, 2006/11/03
- Re: Emacs and GFortran, Alfred M. Szmidt, 2006/11/02
- Re: Emacs and GFortran, Steve Kargl, 2006/11/03
- Re: Emacs and GFortran,
Brooks Moses <=
- Re: Emacs and GFortran, Nick Roberts, 2006/11/03
- Re: Emacs and GFortran, Brooks Moses, 2006/11/03
- Re: Emacs and GFortran, Brooks Moses, 2006/11/14
- Re: Emacs and GFortran, Nick Roberts, 2006/11/14
- Re: Emacs and GFortran, Brooks Moses, 2006/11/15
- Re: Emacs and GFortran, Nick Roberts, 2006/11/15
- Re: Emacs and GFortran, David Kastrup, 2006/11/15
- Re: Emacs and GFortran, David Kastrup, 2006/11/15
- Re: Emacs and GFortran, Andrew Pinski, 2006/11/15
- Re: Emacs and GFortran, David Kastrup, 2006/11/15