This is the mail archive of the 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]

Re: Fwd: [ALL TARGETS] final patch for PR 25241

On 13/07/07, Hans-Peter Nilsson <> 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

We haven't actually fixed that bug yet.

However, it is always better to match each line with its own dg-*
directive, especially if they are mixed warnings and errors, because
dejagnu is quite unpredictable on what it matches when it has the
option to match multiple messages with a single dg directive.

Your ChangeLog entry didn't mention gcc.dg/20011127-1.c (a
target-specific test that predates which now breaks,
because after every line with ``"invalid 'asm': invalid operand
modifier letter"'', the rtx operand is printed.  It used to
match a separate dg-error line but now it doesn't anymore.  It
looks like this in the log:

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.

FAIL: gcc.dg/20011127-1.c (test for excess errors) Excess errors: (reg:SI 9 r9 [25]) (reg:SI 9 r9 [26]) (reg:SI 9 r9 [27]) (reg:SI 9 r9 [28]) (reg:SI 9 r9 [29]) (reg:SI 9 r9 [30]) (reg:SI 9 r9 [31]) (reg:SI 9 r9 [32]) (reg:SI 9 r9 [33]) (reg:SI 9 r9 [34]) (reg:SI 9 r9 [35])

So, how do I match those lines, now that the line

/* { dg-error "reg:SI|const_double:DF" "prune debug_rtx output" { target cris-*-* } 0 } */

doesn't catch it?

Are those errors? I don't see the "error" marker. Perhaps you should try with

/* { dg-message "reg:SI|const_double:DF" "prune debug_rtx output" {
target cris-*-* } 0 } */



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