public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Hongyu Wang <hongyu.wang@intel.com>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] AVX512FP16: Fix vcvt[u]si2sh runtime tests for Solaris
Date: Wed,  2 Mar 2022 09:24:39 +0800	[thread overview]
Message-ID: <20220302012439.33517-1-hongyu.wang@intel.com> (raw)

Use standard C type instead of __int64_t which doesn't work on Solaris.

Tested by Rainer Orth on Solaris/x86. Pushed to trunk as obvious fix.

gcc/testsuite/ChangeLog:

	PR target/104724
	* gcc.target/i386/avx512fp16-vcvtsi2sh-1b.c: Use long long
	instead of __int64_t.
	* gcc.target/i386/avx512fp16-vcvtsi2sh64-1b.c: Ditto.
	* gcc.target/i386/avx512fp16-vcvtusi2sh-1b.c: Ditto.
	* gcc.target/i386/avx512fp16-vcvtusi2sh64-1b.c: Ditto.
---
 gcc/testsuite/gcc.target/i386/avx512fp16-vcvtsi2sh-1b.c    | 2 +-
 gcc/testsuite/gcc.target/i386/avx512fp16-vcvtsi2sh64-1b.c  | 2 +-
 gcc/testsuite/gcc.target/i386/avx512fp16-vcvtusi2sh-1b.c   | 2 +-
 gcc/testsuite/gcc.target/i386/avx512fp16-vcvtusi2sh64-1b.c | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/gcc/testsuite/gcc.target/i386/avx512fp16-vcvtsi2sh-1b.c b/gcc/testsuite/gcc.target/i386/avx512fp16-vcvtsi2sh-1b.c
index d9c9a853a17..7f7e6032e60 100644
--- a/gcc/testsuite/gcc.target/i386/avx512fp16-vcvtsi2sh-1b.c
+++ b/gcc/testsuite/gcc.target/i386/avx512fp16-vcvtsi2sh-1b.c
@@ -9,7 +9,7 @@
 
 void NOINLINE
 emulate_vcvtsi2sh(V512 *dest, V512 op1, 
-		  int value_32, __int64_t value_64, int bits)
+		  int value_32, long long value_64, int bits)
 {
   V512 v1,v2,v5,v6;
   unpack_ph_2twops(op1, &v1, &v2);
diff --git a/gcc/testsuite/gcc.target/i386/avx512fp16-vcvtsi2sh64-1b.c b/gcc/testsuite/gcc.target/i386/avx512fp16-vcvtsi2sh64-1b.c
index 6f66a87a8e7..5bca1905f82 100644
--- a/gcc/testsuite/gcc.target/i386/avx512fp16-vcvtsi2sh64-1b.c
+++ b/gcc/testsuite/gcc.target/i386/avx512fp16-vcvtsi2sh64-1b.c
@@ -9,7 +9,7 @@
 
 void NOINLINE
 emulate_vcvtsi2sh(V512 *dest, V512 op1, 
-		  int value_32, __int64_t value_64, int bits)
+		  int value_32, long long value_64, int bits)
 {
   V512 v1,v2,v5,v6;
   unpack_ph_2twops(op1, &v1, &v2);
diff --git a/gcc/testsuite/gcc.target/i386/avx512fp16-vcvtusi2sh-1b.c b/gcc/testsuite/gcc.target/i386/avx512fp16-vcvtusi2sh-1b.c
index d339f0a4043..e17579cfd3c 100644
--- a/gcc/testsuite/gcc.target/i386/avx512fp16-vcvtusi2sh-1b.c
+++ b/gcc/testsuite/gcc.target/i386/avx512fp16-vcvtusi2sh-1b.c
@@ -9,7 +9,7 @@
 
 void NOINLINE
 emulate_vcvtusi2sh(V512 *dest, V512 op1, 
-		   int value_32, __int64_t value_64, int bits)
+		   int value_32, long long value_64, int bits)
 {
   V512 v1,v2,v5,v6;
   unpack_ph_2twops(op1, &v1, &v2);
diff --git a/gcc/testsuite/gcc.target/i386/avx512fp16-vcvtusi2sh64-1b.c b/gcc/testsuite/gcc.target/i386/avx512fp16-vcvtusi2sh64-1b.c
index 20e711e1b0e..42726bd3d67 100644
--- a/gcc/testsuite/gcc.target/i386/avx512fp16-vcvtusi2sh64-1b.c
+++ b/gcc/testsuite/gcc.target/i386/avx512fp16-vcvtusi2sh64-1b.c
@@ -9,7 +9,7 @@
 
 void NOINLINE
 emulate_vcvtusi2sh(V512 *dest, V512 op1, 
-		   int value_32, __int64_t value_64, int bits)
+		   int value_32, long long value_64, int bits)
 {
   V512 v1,v2,v5,v6;
   unpack_ph_2twops(op1, &v1, &v2);
-- 
2.18.1


                 reply	other threads:[~2022-03-02  1:24 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=20220302012439.33517-1-hongyu.wang@intel.com \
    --to=hongyu.wang@intel.com \
    --cc=gcc-patches@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).