Re: PR78319

2016-11-17 Thread Jeff Law
but it didn't catch the case in PR78319. [1] https://gcc.gnu.org/ml/gcc-patches/2016-11/msg00225.html XFAILing is ok. Agreed. Thanks for checking Prathamesh. Jeff

Re: PR78319

2016-11-17 Thread Richard Biener
> Aldy's enhancements to catch. > Hi Jeff, > I tried Aldy's patch [1], but it didn't catch the case in PR78319. > > [1] https://gcc.gnu.org/ml/gcc-patches/2016-11/msg00225.html XFAILing is ok. Richard. > Thanks, > Prathamesh > > > > jeff > > -- Richard Biener SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)

Re: PR78319

2016-11-16 Thread Prathamesh Kulkarni
the uninit code helps your case > (approved earlier today, so hopefully in the tree very soon). I quickly > scanned the BZ. There's some overlap, but it might be too complex for > Aldy's enhancements to catch. Hi Jeff, I tried Aldy's patch [1], but it didn't catch the

Re: PR78319

2016-11-16 Thread Jeff Law
On 11/16/2016 01:23 PM, Prathamesh Kulkarni wrote: Hi, As discussed in PR, this patch marks the test-case to xfail on arm-none-eabi. OK to commit ? You might check if Aldy's change to the uninit code helps your case (approved earlier today, so hopefully in the tree very soon). I quickly scanne

PR78319

2016-11-16 Thread Prathamesh Kulkarni
(); + /* marking this test as xfail on arm-none-eabi, see PR78319. */ if ( n || m || r || l) - blah(v); /* { dg-bogus "uninitialized" "bogus warning" } */ + blah(v); /* { dg-bogus "uninitialized" "bogus warning" { xfail arm-none-eabi } } */