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

2005-06-02 Thread Richard Sandiford
Diego Novillo <[EMAIL PROTECTED]> 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

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

2005-05-30 Thread 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. D

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

2005-05-30 Thread 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