https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66946
Wilco changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66946
Manuel López-Ibáñez changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66946
--- Comment #4 from Wilco ---
(In reply to Andrew Pinski from comment #2)
> Comment on attachment 36021 [details]
> minimal example
>
> written == ((wchar_t) 0xfffd)
>
> Will ever be true or is there some sign extending going on which causes th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66946
--- Comment #3 from Andrew Pinski ---
Ok. This just looks like a missing jump threading.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66946
--- Comment #2 from Andrew Pinski ---
Comment on attachment 36021
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36021
minimal example
written == ((wchar_t) 0xfffd)
Will ever be true or is there some sign extending going on which causes t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66946
--- Comment #1 from Wilco ---
Created attachment 36021
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36021&action=edit
minimal example
Minimal example which still reports the spurious warning.
