(error_print): Avoid leading space in error lines.
* testsuite/lib/gfortran-dg.exp (gfortran-dg-test): Adjust pattern
for matching error messages.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@118491
138bc75d-0d04-0410-961f-
82ee72b054a4
+2006-11-04 Brooks Moses <brooks.moses@codesourcery.com>
+
+ * error.c (show_locus): Add trailing colon in error messages.
+ (error_print): Avoid leading space in error lines.
+
2006-11-04 Francois-Xavier Coudert <coudert@clipper.ens.fr>
PR fortran/29713
lb = loc->lb;
f = lb->file;
- error_printf ("%s:%d\n", f->filename,
+ error_printf ("%s:%d:\n", f->filename,
#ifdef USE_MAPPED_LOCATION
LOCATION_LINE (lb->location)
#else
if (have_l1)
show_loci (l1, l2);
error_string (type);
- error_char (' ');
+ if (*type)
+ error_char (' ');
have_l1 = 0;
format = format0;
+2006-11-04 Brooks Moses <brooks.moses@codesourcery.com>
+
+ * lib/gfortran-dg.exp (gfortran-dg-test): Adjust pattern
+ for matching error messages.
+
2006-11-04 Uros Bizjak <ubizjak@gmail.com>
PR target/26915
set output_file [lindex $result 1]
# gfortran error messages look like this:
- # [name]:[line]
+ # [name]:[line]:
#
# some code
# 1
# Error: Some error at (1)
# or
- # [name]:[line]
+ # [name]:[line]:
#
# some code
# 1
- # [name]:[line2]
+ # [name]:[line2]:
#
# some other code
# 2
# Error: Some error at (1) and (2)
# or
- # [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 " (\[^\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"