+2006-11-02 Brooks Moses <brooks.moses@codesourcery.com>
+
+ * error.c (show_locus): Remove "In file" from error messages.
+
2006-10-31 Geoffrey Keating <geoffk@apple.com>
* trans-decl.c (gfc_generate_constructors): Update for removal
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
+2006-11-02 Brooks Moses <brooks.moses@codesourcery.com>
+
+ * lib/gfortran-dg.exp (gfortran-dg-test): Remove expected "In file"
+ from error messages.
+
2006-11-02 Mike Stump <mrs@apple.com>
* obj-c++.dg/const-str-9.mm: Don't run on 64-bit.
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
# 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"