| Message ID | ZcpReZzlV3felNFO@tucnak |
|---|---|
| State | New |
| Headers | show |
| Series | testsuite: Fix up gcc.dg/pr113693.c for ia32 | expand |
> Am 12.02.2024 um 18:13 schrieb Jakub Jelinek <jakub@redhat.com>: > > Hi! > > 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. > > Bootstrapped/regtested on x86_64-linux and i686-linux (with the ia32 _BitInt > enablement patch), ok for trunk? Ok > 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. > > --- gcc/testsuite/gcc.dg/pr113693.c.jj 2024-02-01 20:31:40.592630501 +0100 > +++ gcc/testsuite/gcc.dg/pr113693.c 2024-02-12 10:10:30.019384623 +0100 > @@ -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:" } */ > > Jakub >
--- gcc/testsuite/gcc.dg/pr113693.c.jj 2024-02-01 20:31:40.592630501 +0100 +++ gcc/testsuite/gcc.dg/pr113693.c 2024-02-12 10:10:30.019384623 +0100 @@ -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:" } */
Hi! 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. Bootstrapped/regtested on x86_64-linux and i686-linux (with the ia32 _BitInt enablement patch), ok for trunk? 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. Jakub