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-5237] rs6000: Fix typo on vec_vsubcuq in rs6000-overload.def [PR108396]
Date: Wed, 18 Jan 2023 08:35:25 +0000 (GMT)	[thread overview]
Message-ID: <20230118083525.10FD638582BC@sourceware.org> (raw)

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

commit r13-5237-gaaf29ae6cdbaad58b709a77784375d15138174b3
Author: Kewen Lin <linkw@linux.ibm.com>
Date:   Wed Jan 18 02:34:25 2023 -0600

    rs6000: Fix typo on vec_vsubcuq in rs6000-overload.def [PR108396]
    
    As Andrew pointed out in PR108396, there is one typo in
    rs6000-overload.def on built-in function vec_vsubcuq:
    
      [VEC_VSUBCUQ, vec_vsubcuqP, __builtin_vec_vsubcuq]
    
    "vec_vsubcuqP" should be "vec_vsubcuq", this typo caused
    us to define vec_vsubcuqP in rs6000-vecdefines.h instead
    of vec_vsubcuq, so that compiler is not able to realize
    the built-in function name vec_vsubcuq any more.
    
    Co-authored-By: Andrew Pinski <apinski@marvell.com>
    
            PR target/108396
    
    gcc/ChangeLog:
    
            * config/rs6000/rs6000-overload.def (VEC_VSUBCUQ): Fix typo
            vec_vsubcuqP with vec_vsubcuq.
    
    gcc/testsuite/ChangeLog:
    
            * gcc.target/powerpc/pr108396.c: New test.

Diff:
---
 gcc/config/rs6000/rs6000-overload.def       |  2 +-
 gcc/testsuite/gcc.target/powerpc/pr108396.c | 14 ++++++++++++++
 2 files changed, 15 insertions(+), 1 deletion(-)

diff --git a/gcc/config/rs6000/rs6000-overload.def b/gcc/config/rs6000/rs6000-overload.def
index 20cc03107c9..c582490c084 100644
--- a/gcc/config/rs6000/rs6000-overload.def
+++ b/gcc/config/rs6000/rs6000-overload.def
@@ -5930,7 +5930,7 @@
   unsigned int __builtin_vec_scalar_test_data_class_sp (float, const int);
     VSTDCSP  VSTDCSP_DEPR1
 
-[VEC_VSUBCUQ, vec_vsubcuqP, __builtin_vec_vsubcuq]
+[VEC_VSUBCUQ, vec_vsubcuq, __builtin_vec_vsubcuq]
   vsq __builtin_vec_vsubcuq (vsq, vsq);
     VSUBCUQ  VSUBCUQ_DEPR1
   vuq __builtin_vec_vsubcuq (vuq, vuq);
diff --git a/gcc/testsuite/gcc.target/powerpc/pr108396.c b/gcc/testsuite/gcc.target/powerpc/pr108396.c
new file mode 100644
index 00000000000..a783f0823a6
--- /dev/null
+++ b/gcc/testsuite/gcc.target/powerpc/pr108396.c
@@ -0,0 +1,14 @@
+/* { dg-require-effective-target powerpc_p8vector_ok } */
+/* { dg-require-effective-target int128 } */
+/* { dg-options "-mdejagnu-cpu=power8" } */
+
+/* Verify there is no error message.  */
+
+#include <altivec.h>
+
+vector unsigned __int128
+vsubcuq (vector unsigned __int128 a, vector unsigned __int128 b)
+{
+  return vec_vsubcuq (a, b);
+}
+

                 reply	other threads:[~2023-01-18  8:35 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=20230118083525.10FD638582BC@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).