On 4/8/19 3:00 AM, Richard Biener wrote:
> On Fri, Apr 5, 2019 at 2:26 PM Vladislav Ivanishin wrote:
>>
>> Richard Biener writes:
>>
>>> On Thu, Apr 4, 2019 at 4:05 PM Vladislav Ivanishin wrote:
Richard Biener writes:
> On Mon, Apr 1, 2019 at 5:36 PM Vladislav Ivanishin
On Fri, Apr 5, 2019 at 2:26 PM Vladislav Ivanishin wrote:
>
> Richard Biener writes:
>
> > On Thu, Apr 4, 2019 at 4:05 PM Vladislav Ivanishin wrote:
> >>
> >> Richard Biener writes:
> >>
> >> > On Mon, Apr 1, 2019 at 5:36 PM Vladislav Ivanishin
> >> > wrote:
> >> >>
> >> >> Hi!
> >> >>
> >>
Richard Biener writes:
> On Thu, Apr 4, 2019 at 4:05 PM Vladislav Ivanishin wrote:
>>
>> Richard Biener writes:
>>
>> > On Mon, Apr 1, 2019 at 5:36 PM Vladislav Ivanishin wrote:
>> >>
>> >> Hi!
>> >>
>> >> This is a fairly trivial change fixing a false negative in
>> >> -Wmaybe-uninitialized.
On Thu, Apr 4, 2019 at 4:05 PM Vladislav Ivanishin wrote:
>
> Richard Biener writes:
>
> > On Mon, Apr 1, 2019 at 5:36 PM Vladislav Ivanishin wrote:
> >>
> >> Hi!
> >>
> >> This is a fairly trivial change fixing a false negative in
> >> -Wmaybe-uninitialized. I am pretty sure this is simply an
Richard Biener writes:
> On Mon, Apr 1, 2019 at 5:36 PM Vladislav Ivanishin wrote:
>>
>> Hi!
>>
>> This is a fairly trivial change fixing a false negative in
>> -Wmaybe-uninitialized. I am pretty sure this is simply an overlooked
>> case (is_value_included_in() is not meant to deal with the
On Mon, Apr 1, 2019 at 5:36 PM Vladislav Ivanishin wrote:
>
> Hi!
>
> This is a fairly trivial change fixing a false negative in
> -Wmaybe-uninitialized. I am pretty sure this is simply an overlooked
> case (is_value_included_in() is not meant to deal with the case where
> both compare codes are
Hi!
This is a fairly trivial change fixing a false negative in
-Wmaybe-uninitialized. I am pretty sure this is simply an overlooked
case (is_value_included_in() is not meant to deal with the case where
both compare codes are NE_EXPRs, neither does it need to, since their
handling is trivial).