public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Kewen Lin <linkw@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-2332] rs6000/test: Fix typo in pr86731-fwrapv-longlong.c [PR106682]
Date: Thu,  1 Sep 2022 05:28:03 +0000 (GMT)	[thread overview]
Message-ID: <20220901052803.BAB5C3854150@sourceware.org> (raw)

https://gcc.gnu.org/g:023c5b36e476976cb3b45ff32c7c64990c5a6d45

commit r13-2332-g023c5b36e476976cb3b45ff32c7c64990c5a6d45
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Thu Sep 1 00:27:11 2022 -0500

    rs6000/test: Fix typo in pr86731-fwrapv-longlong.c [PR106682]
    
    Commit r12-2266 updated the scanned assembly content from
    
      "{\mlvx\M|\mlxv\M|\mlxvd2x\M}"
    
    to
    
      "{\mp?lxv\M|\mlxv\M|\mlxvd2x\M}"
    
    for the test case pr86731-fwrapv-longlong.c unexpectedly.
    
    It's meant to update "lxv" to "p?lxv", should leave the
    "lvx" unchanged.  So fix the typo accordingly.
    
            PR testsuite/106682
    
    gcc/testsuite/ChangeLog:
    
            * gcc.target/powerpc/pr86731-fwrapv-longlong.c: Fix typo.

Diff:
---
 gcc/testsuite/gcc.target/powerpc/pr86731-fwrapv-longlong.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.target/powerpc/pr86731-fwrapv-longlong.c b/gcc/testsuite/gcc.target/powerpc/pr86731-fwrapv-longlong.c
index dcb30e1d886..018e1cf9749 100644
--- a/gcc/testsuite/gcc.target/powerpc/pr86731-fwrapv-longlong.c
+++ b/gcc/testsuite/gcc.target/powerpc/pr86731-fwrapv-longlong.c
@@ -31,5 +31,5 @@ vector signed long long splats4(void)
 
 /* { dg-final { scan-assembler-times {\mvspltis[bhw]\M} 0 } } */
 /* { dg-final { scan-assembler-times {\mvsl[bhwd]\M} 0 } } */
-/* { dg-final { scan-assembler-times {\mp?lxv\M|\mlxv\M|\mlxvd2x\M|\mxxspltidp\M} 2 } } */
+/* { dg-final { scan-assembler-times {\mp?lxv\M|\mlvx\M|\mlxvd2x\M|\mxxspltidp\M} 2 } } */

                 reply	other threads:[~2022-09-01  5:28 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=20220901052803.BAB5C3854150@sourceware.org \
    --to=linkw@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).