From: Jakub Jelinek <jakub@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] testsuite: Add another bitint testcase [PR113691]
Date: Fri, 2 Feb 2024 10:58:39 +0100 [thread overview]
Message-ID: <Zby8z2sVUyVjtB5O@tucnak> (raw)
Hi!
This is fixed by the PR113692 patch.
Will commit as obvious if that patch makes it in.
2024-02-02 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/113691
* gcc.dg/bitint-83.c: New test.
--- gcc/testsuite/gcc.dg/bitint-83.c.jj 2024-02-01 12:32:39.555709390 +0100
+++ gcc/testsuite/gcc.dg/bitint-83.c 2024-02-01 12:32:31.178826835 +0100
@@ -0,0 +1,23 @@
+/* PR tree-optimization/113691 */
+/* { dg-do compile { target bitint } } */
+/* { dg-options "-O2 -std=gnu11 -w" } */
+
+#if __BITINT_MAXWIDTH__ >= 944
+_BitInt (944) i;
+#else
+_BitInt (63) i;
+#endif
+
+void foo ();
+
+void
+bar ()
+{
+ foo (i);
+}
+
+void
+foo (int *p)
+{
+ *p = 0;
+}
Jakub
reply other threads:[~2024-02-02 9:58 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=Zby8z2sVUyVjtB5O@tucnak \
--to=jakub@redhat.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).