[gcc r14-8938] testsuite: Fix up gcc.dg/pr113693.c for ia32

[gcc r14-8938] testsuite: Fix up gcc.dg/pr113693.c for ia32

[Jakub Jelinek]

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:" } */