public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r14-8938] testsuite: Fix up gcc.dg/pr113693.c for ia32 Date: Mon, 12 Feb 2024 17:52:37 +0000 (GMT) [thread overview] Message-ID: <20240212175237.9F223385840D@sourceware.org> (raw) https://gcc.gnu.org/g:76fb83559dc85d9a6de92c0505cf5c4dfa698430 commit r14-8938-g76fb83559dc85d9a6de92c0505cf5c4dfa698430 Author: Jakub Jelinek <jakub@redhat.com> Date: Mon Feb 12 18:51:25 2024 +0100 testsuite: Fix up gcc.dg/pr113693.c for ia32 As I wrote earlier and we've discussed on IRC, with the ia32 _BitInt enablement patch this testcase FAILs on ia32, there is nothing vectorized in there, even with -mavx512{vl,bw,dq}, so no dbgcnt messages are emitted. The following patch instead prunes it. 2024-02-12 Jakub Jelinek <jakub@redhat.com> * gcc.dg/pr113693.c: Guard _BitInt(837) use with __BITINT_MAXWIDTH__ >= 837. Use dg-prune-output instead of dg-message for dbgcnt message. Diff: --- gcc/testsuite/gcc.dg/pr113693.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/gcc/testsuite/gcc.dg/pr113693.c b/gcc/testsuite/gcc.dg/pr113693.c index a6f55199d0ff..06b44357f082 100644 --- a/gcc/testsuite/gcc.dg/pr113693.c +++ b/gcc/testsuite/gcc.dg/pr113693.c @@ -1,7 +1,11 @@ /* { dg-do compile { target bitint } } */ /* { dg-options "-O2 -fdbg-cnt=vect_loop:1" } */ +#if __BITINT_MAXWIDTH__ >= 837 _BitInt(837) g, h; +#else +_BitInt(63) g, h; +#endif void fn1(void) @@ -10,4 +14,5 @@ fn1(void) for (; h; h++) ; } -/* { dg-message "dbgcnt" "" { target *-*-* } 0 } */ + +/* { dg-prune-output "dbgcnt:" } */
reply other threads:[~2024-02-12 17:52 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=20240212175237.9F223385840D@sourceware.org \ --to=jakub@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: linkBe 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).