From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: "Maciej W. Rozycki" <macro@embecosm.com>, gcc-patches@gcc.gnu.org
Cc: Richard Sandiford <richard.sandiford@arm.com>,
Marcus Shawcroft <marcus.shawcroft@arm.com>,
Kyrylo Tkachov <kyrylo.tkachov@arm.com>,
Jeff Law <jeffreyalaw@gmail.com>
Subject: Re: [PATCH] AArch64/testsuite: Use non-capturing parentheses with ccmp_1.c
Date: Wed, 22 Nov 2023 16:18:46 +0000 [thread overview]
Message-ID: <e2f33299-e925-a8f6-36cd-ba547397f409@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.20.2311221501050.5892@tpp.orcam.me.uk>
On 22/11/2023 15:21, Maciej W. Rozycki wrote:
> Use non-capturing parentheses for the subexpressions used with
> `scan-assembler-times', to avoid a quirk with double-counting.
>
> gcc/testsuite/
> * gcc.target/aarch64/ccmp_1.c: Use non-capturing parentheses
> with `scan-assembler-times'.
OK
R.
> ---
> Hi,
>
> Here's another one. I realised my original regexp used to grep the tree
> for `scan-assembler-times' with subexpressions was too strict and with an
> updated pattern I found this second test case that does regress once the
> `scan-assembler-times' double-counting quirk has been fixed.
>
> As with the ARM change we don't need capturing parentheses here, usually
> used for back references, so let's just avoid the double-counting quirk
> altogether and make our matching here work whether the quirk has been
> fixed or not.
>
> Verified for the `aarch64-linux-gnu' target with the quirk fix submitted
> as <https://gcc.gnu.org/pipermail/gcc-patches/2023-November/637254.html>
> and the aarch64.exp subset of the C language test suite. OK to apply?
>
> Maciej
> ---
> gcc/testsuite/gcc.target/aarch64/ccmp_1.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> gcc-aarch64-test-ccmp_1-non-capturing.diff
> Index: gcc/gcc/testsuite/gcc.target/aarch64/ccmp_1.c
> ===================================================================
> --- gcc.orig/gcc/testsuite/gcc.target/aarch64/ccmp_1.c
> +++ gcc/gcc/testsuite/gcc.target/aarch64/ccmp_1.c
> @@ -86,8 +86,8 @@ f13 (int a, int b)
> /* { dg-final { scan-assembler "cmp\t(.)+35" } } */
>
> /* { dg-final { scan-assembler-times "\tcmp\tw\[0-9\]+, 0" 4 } } */
> -/* { dg-final { scan-assembler-times "fcmpe\t(.)+0\\.0" 2 } } */
> -/* { dg-final { scan-assembler-times "fcmp\t(.)+0\\.0" 2 } } */
> +/* { dg-final { scan-assembler-times "fcmpe\t(?:.)+0\\.0" 1 } } */
> +/* { dg-final { scan-assembler-times "fcmp\t(?:.)+0\\.0" 1 } } */
>
> /* { dg-final { scan-assembler "adds\t" } } */
> /* { dg-final { scan-assembler-times "\tccmp\t" 11 } } */
next prev parent reply other threads:[~2023-11-22 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 15:21 Maciej W. Rozycki
2023-11-22 16:18 ` Richard Earnshaw (lists) [this message]
2023-11-23 16:20 ` Maciej W. Rozycki
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=e2f33299-e925-a8f6-36cd-ba547397f409@arm.com \
--to=richard.earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=kyrylo.tkachov@arm.com \
--cc=macro@embecosm.com \
--cc=marcus.shawcroft@arm.com \
--cc=richard.sandiford@arm.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).