https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90424
--- Comment #11 from Matthias Kretz (Vir) ---
"two undef reads should end up the same value" folks are unreasonable anyway.
;) Losing diagnostics would be unfortunate. But I don't have enough context
here.
don't know if this helps:
FWIW, I've s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90424
--- Comment #10 from Richard Biener ---
(In reply to Andrew Pinski from comment #9)
> Hmm, we get:
> BIT_INSERT_EXPR ;
>
> Since r_5 is unintialized, can't we just do:
> {_1, 0}
>
> ?
Yes. Though I always get nervous when replacing a UNDEF wi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90424
--- Comment #9 from Andrew Pinski ---
Hmm, we get:
BIT_INSERT_EXPR ;
Since r_5 is unintialized, can't we just do:
{_1, 0}
?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90424
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed|2019-05-13 00:00:00 |2021-9-4
Severity|normal
