From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <rguenther@suse.de>,
Florian Weimer <fweimer@redhat.com>,
Jeff Law <jeffreyalaw@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: [PATCH] testsuite: Tweak some further tests for modern C changes
Date: Fri, 1 Dec 2023 12:27:19 +0100 [thread overview]
Message-ID: <ZWnDFz+FcrkpsHzE@tucnak> (raw)
Hi!
On IRC Richi mentioned some FAILs in gcc.target/x86_64 and in pr83126.c.
The following patch fixes the former ones (they need recent binutils to
be enabled), for pr83126.c because I didn't have graphite configured I've
just verified that the test compiles (didn't without the patch) and that
the gimple dump is identical with one from yesterday's gcc (as it was a
tree-parloops.cc ICE, I guess identical gimple is all we care about
and no need to verify it further).
Ok for trunk?
2023-12-01 Jakub Jelinek <jakub@redhat.com>
* gcc.target/x86_64/abi/avx512fp16/m512h/test_passing_m512.c
(fun_check_passing_m512_8_values, fun_check_passing_m512h_8_values):
Add missing void return type.
* gcc.target/x86_64/abi/avx512fp16/m256h/test_passing_m256.c
(fun_check_passing_m256_8_values, fun_check_passing_m256h_8_values):
Likewise.
* gcc.dg/graphite/pr83126.c (ew): Add missing casts to __INTPTR_TYPE__
and then to int *.
--- gcc/testsuite/gcc.target/x86_64/abi/avx512fp16/m512h/test_passing_m512.c.jj 2021-12-30 15:12:43.747143127 +0100
+++ gcc/testsuite/gcc.target/x86_64/abi/avx512fp16/m512h/test_passing_m512.c 2023-12-01 11:56:10.708574470 +0100
@@ -25,6 +25,7 @@ int failed = 0;
assert (memcmp (&X1, &X2, sizeof (T)) == 0); \
} while (0)
+void
fun_check_passing_m512_8_values (__m512 i0 ATTRIBUTE_UNUSED,
__m512 i1 ATTRIBUTE_UNUSED,
__m512 i2 ATTRIBUTE_UNUSED,
@@ -45,6 +46,7 @@ fun_check_passing_m512_8_values (__m512
compare (values.i7, i7, __m512);
}
+void
fun_check_passing_m512h_8_values (__m512h i0 ATTRIBUTE_UNUSED,
__m512h i1 ATTRIBUTE_UNUSED,
__m512h i2 ATTRIBUTE_UNUSED,
--- gcc/testsuite/gcc.target/x86_64/abi/avx512fp16/m256h/test_passing_m256.c.jj 2021-12-30 15:12:43.746143141 +0100
+++ gcc/testsuite/gcc.target/x86_64/abi/avx512fp16/m256h/test_passing_m256.c 2023-12-01 11:55:56.770772491 +0100
@@ -25,6 +25,7 @@ int failed = 0;
assert (memcmp (&X1, &X2, sizeof (T)) == 0); \
} while (0)
+void
fun_check_passing_m256_8_values (__m256 i0 ATTRIBUTE_UNUSED,
__m256 i1 ATTRIBUTE_UNUSED,
__m256 i2 ATTRIBUTE_UNUSED,
@@ -45,6 +46,7 @@ fun_check_passing_m256_8_values (__m256
compare (values.i7, i7, __m256);
}
+void
fun_check_passing_m256h_8_values (__m256h i0 ATTRIBUTE_UNUSED,
__m256h i1 ATTRIBUTE_UNUSED,
__m256h i2 ATTRIBUTE_UNUSED,
--- gcc/testsuite/gcc.dg/graphite/pr83126.c.jj 2020-01-12 11:54:37.438397944 +0100
+++ gcc/testsuite/gcc.dg/graphite/pr83126.c 2023-12-01 12:20:42.045695863 +0100
@@ -12,7 +12,7 @@ ew (unsigned short int c9, int stuff)
int *fd = &stuff;
*fd = c9;
- fd = *fd;
+ fd = (int *) (__INTPTR_TYPE__) *fd;
if (*fd != 0)
for (*by = 0; *by < 2; ++*by)
c9 *= e1;
Jakub
next reply other threads:[~2023-12-01 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 11:27 Jakub Jelinek [this message]
2023-12-01 11:24 ` Richard Biener
2023-12-01 11:37 ` Florian Weimer
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=ZWnDFz+FcrkpsHzE@tucnak \
--to=jakub@redhat.com \
--cc=fweimer@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=rguenther@suse.de \
/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).