Commit cb60c134 by Brooks Moses Committed by Brooks Moses

error.c (show_locus): Add trailing colon in error messages.

* fortran/error.c (show_locus): Add trailing colon in error messages.
(error_print): Avoid leading space in error lines.
* testsuite/lib/gfortran-dg.exp (gfortran-dg-test): Adjust pattern
for matching error messages.

From-SVN: r118491
parent 48728882
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> 2006-11-04 Francois-Xavier Coudert <coudert@clipper.ens.fr>
PR fortran/29713 PR fortran/29713
......
...@@ -134,7 +134,7 @@ show_locus (int offset, locus * loc) ...@@ -134,7 +134,7 @@ show_locus (int offset, locus * loc)
lb = loc->lb; lb = loc->lb;
f = lb->file; f = lb->file;
error_printf ("%s:%d\n", f->filename, error_printf ("%s:%d:\n", f->filename,
#ifdef USE_MAPPED_LOCATION #ifdef USE_MAPPED_LOCATION
LOCATION_LINE (lb->location) LOCATION_LINE (lb->location)
#else #else
...@@ -380,7 +380,8 @@ error_print (const char *type, const char *format0, va_list argp) ...@@ -380,7 +380,8 @@ error_print (const char *type, const char *format0, va_list argp)
if (have_l1) if (have_l1)
show_loci (l1, l2); show_loci (l1, l2);
error_string (type); error_string (type);
error_char (' '); if (*type)
error_char (' ');
have_l1 = 0; have_l1 = 0;
format = format0; 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> 2006-11-04 Uros Bizjak <ubizjak@gmail.com>
PR target/26915 PR target/26915
...@@ -26,23 +26,23 @@ proc gfortran-dg-test { prog do_what extra_tool_flags } { ...@@ -26,23 +26,23 @@ proc gfortran-dg-test { prog do_what extra_tool_flags } {
set output_file [lindex $result 1] set output_file [lindex $result 1]
# gfortran error messages look like this: # gfortran error messages look like this:
# [name]:[line] # [name]:[line]:
# #
# some code # some code
# 1 # 1
# Error: Some error at (1) # Error: Some error at (1)
# or # or
# [name]:[line] # [name]:[line]:
# #
# some code # some code
# 1 # 1
# [name]:[line2] # [name]:[line2]:
# #
# some other code # some other code
# 2 # 2
# Error: Some error at (1) and (2) # Error: Some error at (1) and (2)
# or # or
# [name]:[line] # [name]:[line]:
# #
# some code and some more code # some code and some more code
# 1 2 # 1 2
...@@ -59,7 +59,7 @@ proc gfortran-dg-test { prog do_what extra_tool_flags } { ...@@ -59,7 +59,7 @@ proc gfortran-dg-test { prog do_what extra_tool_flags } {
# Note that these regexps only make sense in the combinations used below. # 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 # Note also that is imperative that we first deal with the form with
# two loci. # 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 diag_regexp "(\[^\n\]*)\n"
set two_loci "$locus_regexp$locus_regexp$diag_regexp" set two_loci "$locus_regexp$locus_regexp$diag_regexp"
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment