This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Problem with scan-tree-dump-times in dg.exp
- From: Jeffrey A Law <law at redhat dot com>
- To: Diego Novillo <dnovillo at redhat dot com>
- Cc: gcc at gcc dot gnu dot org, Janis Johnson <janis187 at us dot ibm dot com>
- Date: Mon, 30 May 2005 11:03:24 -0600
- Subject: Re: Problem with scan-tree-dump-times in dg.exp
- References: <20050530163202.GA21036@topo.toronto.redhat.com>
- Reply-to: law at redhat dot com
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