Re: C++ PATCH to fix bogus maybe-uninitialized warning (PR c++/80119)

2017-04-07 Thread Jason Merrill
On Tue, Mar 21, 2017 at 6:00 PM, Marek Polacek wrote: > On Tue, Mar 21, 2017 at 08:41:01PM +0100, Jakub Jelinek wrote: >> On Tue, Mar 21, 2017 at 03:27:02PM -0400, Jason Merrill wrote: >> > OK. >> > >> > On Tue, Mar 21, 2017 at 11:38 AM, Marek Polacek

Re: C++ PATCH to fix bogus maybe-uninitialized warning (PR c++/80119)

2017-03-21 Thread Marek Polacek
On Tue, Mar 21, 2017 at 08:41:01PM +0100, Jakub Jelinek wrote: > On Tue, Mar 21, 2017 at 03:27:02PM -0400, Jason Merrill wrote: > > OK. > > > > On Tue, Mar 21, 2017 at 11:38 AM, Marek Polacek wrote: > > > This patch fixes a bogus maybe-uninitialized warning reported in the

Re: C++ PATCH to fix bogus maybe-uninitialized warning (PR c++/80119)

2017-03-21 Thread Jakub Jelinek
On Tue, Mar 21, 2017 at 03:27:02PM -0400, Jason Merrill wrote: > OK. > > On Tue, Mar 21, 2017 at 11:38 AM, Marek Polacek wrote: > > This patch fixes a bogus maybe-uninitialized warning reported in the PR. > > The issue is that we're not able to fold away useless

Re: C++ PATCH to fix bogus maybe-uninitialized warning (PR c++/80119)

2017-03-21 Thread Jason Merrill
OK. On Tue, Mar 21, 2017 at 11:38 AM, Marek Polacek wrote: > This patch fixes a bogus maybe-uninitialized warning reported in the PR. > The issue is that we're not able to fold away useless CLEANUP_POINT_EXPRs, > as e.g. in > if (<>) >// bogus warning > Here, the

C++ PATCH to fix bogus maybe-uninitialized warning (PR c++/80119)

2017-03-21 Thread Marek Polacek
This patch fixes a bogus maybe-uninitialized warning reported in the PR. The issue is that we're not able to fold away useless CLEANUP_POINT_EXPRs, as e.g. in if (<>) // bogus warning Here, the cleanup_point was built as <>, which cp_fold_r reduces to <>, but leaves it as that and passes it