public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kaveh R. GHAZI" <ghazi@caip.rutgers.edu>
To: Steve Ellcey <sje@cup.hp.com>
Cc: gcc@gcc.gnu.org, janis187@us.ibm.com
Subject: Re: Testsuite regular expression question
Date: Tue, 27 Oct 2009 10:38:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.58.0910270201450.4284@caipclassic.rutgers.edu> (raw)
In-Reply-To: <200910262306.n9QN6u113854@lucas.cup.hp.com>

On Mon, 26 Oct 2009, Steve Ellcey wrote:

> I have tried:
> /* { dg-final { scan-assembler-times "(byte|data1).*?0x3.*? DW_AT_inline" 3 } } */
> /* { dg-final { scan-assembler-times "(byte\|data1).*?0x3.*? DW_AT_inline" 3 } } */
> /* { dg-final { scan-assembler-times "\(byte\|data1\).*?0x3.*? DW_AT_inline" 3 } } */
>
> And various other escapes, parenthesis, etc but cannot get any of them
> to work.  Does anyone know what this RE should look like to allow 'byte'
> or 'data1' in the string?  It seems to break as soon as I introduce
> parenthesis anywhere in the RE.

I think you need two backslashes escaping the paren and maybe one before
the pipe.  I'm not sure about the \| vs | though, give the double escape
paren a try both ways.  You can see some examples via:

	find gcc/testsuite | xargs grep 'scan-assembler-times.*[(|]'

		--Kaveh

  reply	other threads:[~2009-10-27  6:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26 23:35 Steve Ellcey
2009-10-27 10:38 ` Kaveh R. GHAZI [this message]
2009-10-27 17:00   ` Steve Ellcey
2009-10-27 17:13     ` Andreas Schwab
2009-10-27 17:22       ` Steve Ellcey
2009-10-27 20:18         ` Andreas Schwab
2009-10-27 17:16   ` Steve Ellcey
2009-10-27 12:03 ` Andreas Schwab

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=Pine.GSO.4.58.0910270201450.4284@caipclassic.rutgers.edu \
    --to=ghazi@caip.rutgers.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=janis187@us.ibm.com \
    --cc=sje@cup.hp.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).