From: Richard Sandiford <rsandifo@redhat.com>
To: Diego Novillo <dnovillo@redhat.com>
Cc: Jeffrey A Law <law@redhat.com>,
gcc@gcc.gnu.org, Janis Johnson <janis187@us.ibm.com>
Subject: Re: Problem with scan-tree-dump-times in dg.exp
Date: Thu, 02 Jun 2005 10:38:00 -0000 [thread overview]
Message-ID: <87is0xujq8.fsf@firetop.home> (raw)
In-Reply-To: <20050530171826.GA24072@topo.toronto.redhat.com> (Diego Novillo's message of "Mon, 30 May 2005 13:18:26 -0400")
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
prev parent reply other threads:[~2005-06-02 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 17:34 Diego Novillo
2005-05-30 18:03 ` Jeffrey A Law
2005-05-30 18:10 ` Diego Novillo
2005-06-02 10:38 ` Richard Sandiford [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87is0xujq8.fsf@firetop.home \
--to=rsandifo@redhat.com \
--cc=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=janis187@us.ibm.com \
--cc=law@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).