On Wed, Apr 14, 2021 at 07:50:37PM +0200, Jakub Jelinek wrote: > On Wed, Apr 14, 2021 at 10:49:42AM -0600, Martin Sebor via Gcc-patches wrote: > > Apparently the IL GCC emits on some targets (arm and aarach64 with > > mabi=ilp32, and powerpc64 to name the three where the failures have > > been pointed out) isn't handled by the uninit pass and so it doesn't > > issue the expected warning. That might be a new (as in previously > > unknown) limitation in the warning or one I don't remember coming > > across. > > > > I don't see excess warnings with my arm-eabi cross-compiler. What > > are they in your environment? > > > > I have limited the test to just x86_64 for now and repurposed pr100073 > > where the same failure was reported on powerpc64 to track the missing > > warning on these targets. > > + The test fails on a number of non-x86_64 targets due to pr100073. > + { dg-do compile { target x86_64-*-* } } > > change is incorrect.
I have tested it and the test works the same for -m64/-m32/-mx32, therefore I chose: > or you mean x86_64 -m64/-mx32/-m32, then it should be > { i?86-*-* x86_64-*-* } Tested on x86_64-linux and i686-linux, committed to trunk. 2021-04-15 Jakub Jelinek <ja...@redhat.com> PR testsuite/100073 * gcc.dg/pr86058.c: Enable also on i?86-*-*. --- gcc/testsuite/gcc.dg/pr86058.c.jj 2021-04-15 10:40:33.449919170 +0200 +++ gcc/testsuite/gcc.dg/pr86058.c 2021-04-15 14:04:02.247335188 +0200 @@ -1,7 +1,7 @@ /* PR middle-end/86058 - TARGET_MEM_REF causing incorrect message for -Wmaybe-uninitialized warning - The test fails on a number of non-x86_64 targets due to pr100073. - { dg-do compile { target x86_64-*-* } } + The test fails on a number of non-x86 targets due to pr100073. + { dg-do compile { target i?86-*-* x86_64-*-* } } { dg-options "-O2 -Wuninitialized -Wmaybe-uninitialized" } */ extern void foo (int *); Jakub