This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Committed: fix gcc.dg/20011127-1.c fallout from "[ALL TARGETS] final patch for PR 25241"


On Fri, 13 Jul 2007, Manuel López-Ibáñez wrote:

> On 13/07/07, Hans-Peter Nilsson <hp@bitrange.com> wrote:
> > On Tue, 10 Jul 2007, Manuel López-Ibáñez wrote:
> > > Unfortunately, I cannot test anything else apart from
> > > i686-pc-gnu-linux. Thus, some testcases that currently do nasty things
> > > (like matching multiple error/warnings with one dg-error or dg-warning
> > > directive) may break.
> >
> > The question arises: how to match multiple lines now?
>
> Multiple lines match more or less as before. Thus, /* { dg-error "this
> is an error" } */ will still match:
>
> error: this is an error
> error: this is an error

A dg-error used to match lines without the error too, that's
the difference I saw.

> You can use svn diff or svn log --verbose to check whether I modified
> gcc.dg/20011127-1.c. My guess is that I didn't, ergo, it doesn't
> appear in the Changelog.

Right; the framework, not the patch changed.  My mistake.

> Are those errors? I don't see the "error" marker.

They are part of the error message that started on the previous
line.

> Perhaps you should try with
>
> /* { dg-message "reg:SI|const_double:DF" "prune debug_rtx output" {
> target cris-*-* } 0 } */

That worked, thanks.  Committed.

gcc/testsuite:

	* gcc.dg/20011127-1.c: Use dg-message, not dg-error to match the
	error message part that continues on a new line.

Index: gcc.dg/20011127-1.c
===================================================================
--- gcc.dg/20011127-1.c	(revision 126617)
+++ gcc.dg/20011127-1.c	(working copy)
@@ -1,11 +1,11 @@
-/* Copyright (C) 2001  Free Software Foundation.
+/* Copyright (C) 2001, 2007  Free Software Foundation.
    by Hans-Peter Nilsson  <hp@axis.com>

    Making sure that invalid asm operand modifiers don't cause an ICE.  */

 /* { dg-do compile { target cris-*-* } } */
 /* { dg-options "-O2" } */
-/* { dg-error "reg:SI|const_double:DF" "prune debug_rtx output" { target cris-*-* } 0 } */
+/* { dg-message "reg:SI|const_double:DF" "prune debug_rtx output" { target cris-*-* } 0 } */

 void
 foo (void)

brgds, H-P


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]