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
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
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
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
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