Problem with scan-tree-dump-times in dg.exp

Problem with scan-tree-dump-times in dg.exp

[Diego Novillo]

I have a new test case where the dump file ought to have 2
occurrences of the pattern "PREDICATE: p.* ne_expr 0B", so I
added

/* { dg-final { scan-tree-dump-times "PREDICATE: p.* ne_expr 0B" 2 "vrp" } } */

but I'm getting a dump scan failure on that file.  I have
manually checked the dump file and there are 2 instances of
that pattern:

$ grep 'PREDICATE: p.* ne_expr 0B' vrp07.c.t23.vrp
        PREDICATE: p_5 ne_expr 0B
	PREDICATE: p_5 ne_expr 0B

I can't seem to find other test cases with similar patterns.  And
the verbose flags don't show anything obvious.


Thanks.  Diego.

Re: Problem with scan-tree-dump-times in dg.exp

[Jeffrey A Law]

On Mon, 2005-05-30 at 12:32 -0400, Diego Novillo wrote:
> I have a new test case where the dump file ought to have 2
> occurrences of the pattern "PREDICATE: p.* ne_expr 0B", so I
> added
> 
> /* { dg-final { scan-tree-dump-times "PREDICATE: p.* ne_expr 0B" 2 "vrp" } } */
> 
> but I'm getting a dump scan failure on that file.  I have
> manually checked the dump file and there are 2 instances of
> that pattern:
> 
> $ grep 'PREDICATE: p.* ne_expr 0B' vrp07.c.t23.vrp
>         PREDICATE: p_5 ne_expr 0B
> 	PREDICATE: p_5 ne_expr 0B
> 
> I can't seem to find other test cases with similar patterns.  And
> the verbose flags don't show anything obvious.
When faced with this kind of problem, I usually start debugging
by removing all the wildcards and checking for the exact pattern
which appears in the output file.  In this case I'd replace the
.* with _5 and see if it matches properly.  If it does, then I'd
tighten the wildcard.  Something like p_[0-9]*

Jeff

Re: Problem with scan-tree-dump-times in dg.exp

[Diego Novillo]

On Mon, May 30, 2005 at 11:03:24AM -0600, Jeffrey A Law wrote:

> In this case I'd replace the .* with _5 and see if it matches
> properly.  If it does, then I'd tighten the wildcard.
> Something like p_[0-9]*
> 
Excellent, that worked.  I wonder why is dejagnu so fussy about
patterns.


Thanks.  Diego.

Re: Problem with scan-tree-dump-times in dg.exp

[Richard Sandiford]

Diego Novillo <dnovillo@redhat.com> writes:
> On Mon, May 30, 2005 at 11:03:24AM -0600, Jeffrey A Law wrote:
>> In this case I'd replace the .* with _5 and see if it matches
>> properly.  If it does, then I'd tighten the wildcard.
>> Something like p_[0-9]*
>> 
> Excellent, that worked.  I wonder why is dejagnu so fussy about
> patterns.

If I remember right, dejagnu (Tcl?) is unusual in that "." can even
match newline characters.  The original wildcard would then have matched
everything from the first PREDICATE to the final "ne_expr 0B".

Richard