public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jose E. Marchesi <jemarch@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-1951] testsuite: btf: fix regexps in btf-int-1.c
Date: Wed,  3 Aug 2022 16:53:16 +0000 (GMT)	[thread overview]
Message-ID: <20220803165316.2536F3858C39@sourceware.org> (raw)

https://gcc.gnu.org/g:f0688c82ba8206a3d8960eb1d4821dc6a5f2a9f4

commit r13-1951-gf0688c82ba8206a3d8960eb1d4821dc6a5f2a9f4
Author: Jose E. Marchesi <jose.marchesi@oracle.com>
Date:   Wed Aug 3 18:50:05 2022 +0200

    testsuite: btf: fix regexps in btf-int-1.c
    
    The regexps in hte test btf-int-1.c were not working properly with the
    commenting style of at least one target: powerpc64le-linux-gnu.  This
    patch changes the test to use better regexps.
    
    Tested in bpf-unkonwn-none, x86_64-linux-gnu and powerpc64le-linux-gnu.
    Pushed to master as obvious.
    
    gcc/testsuite/ChangeLog:
    
            PR testsuite/106515
            * gcc.dg/debug/btf/btf-int-1.c: Fix regexps in
            scan-assembler-times.

Diff:
---
 gcc/testsuite/gcc.dg/debug/btf/btf-int-1.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/gcc/testsuite/gcc.dg/debug/btf/btf-int-1.c b/gcc/testsuite/gcc.dg/debug/btf/btf-int-1.c
index 87d9758e9cb..e1ed198131a 100644
--- a/gcc/testsuite/gcc.dg/debug/btf/btf-int-1.c
+++ b/gcc/testsuite/gcc.dg/debug/btf/btf-int-1.c
@@ -18,10 +18,10 @@
 /* { dg-final { scan-assembler-times "\[\t \]0x1000000\[\t \]+\[^\n\]*btt_info" 9 } } */
 
 /* Check the signed flags, but not bit size. */
-/* { dg-final { scan-assembler-times "\[\t \]0x10000..\[\t \]+\[^\n\]*bti_encoding" 4 } } */
-/* { dg-final { scan-assembler-times "\[\t \]0x..\[\t \]+\[^\n\]*bti_encoding" 3 } } */
-/* { dg-final { scan-assembler-times "\[\t \]0x.\[\t \]+\[^\n\]*bti_encoding" 1 } } */
-/* { dg-final { scan-assembler-times "\[\t \]0x40000..\[\t \]+\[^\n\]*bti_encoding" 1 } } */
+/* { dg-final { scan-assembler-times "\[\t \]0x10000\[0-9a-zA-Z\]{2}\[\t \]+\[^\n\]*bti_encoding" 4 } } */
+/* { dg-final { scan-assembler-times "\[\t \]0x\[0-9a-zA-Z\]{2}\[\t \]+\[^\n\]*bti_encoding" 3 } } */
+/* { dg-final { scan-assembler-times "\[\t \]0x\[0-9a-zA-Z\]\[\t \]+\[^\n\]*bti_encoding" 1 } } */
+/* { dg-final { scan-assembler-times "\[\t \]0x40000\[0-9a-zA-Z\]{2}\[\t \]+\[^\n\]*bti_encoding" 1 } } */
 
 /* Check that there is a string entry for each type name.  */
 /* { dg-final { scan-assembler-times "ascii \"unsigned char.0\"\[\t \]+\[^\n\]*btf_string" 1 } } */


                 reply	other threads:[~2022-08-03 16:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220803165316.2536F3858C39@sourceware.org \
    --to=jemarch@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /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).