[Bug tree-optimization/66946] Spurious uninitialized warning

2016-09-05 Thread wdijkstr at arm dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66946 Wilco changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug tree-optimization/66946] Spurious uninitialized warning

2016-09-03 Thread manu at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66946 Manuel López-Ibáñez changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug tree-optimization/66946] Spurious uninitialized warning

2015-07-21 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66946 --- Comment #2 from Andrew Pinski pinskia at gcc dot gnu.org --- 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

[Bug tree-optimization/66946] Spurious uninitialized warning

2015-07-21 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66946 --- Comment #3 from Andrew Pinski pinskia at gcc dot gnu.org --- Ok. This just looks like a missing jump threading.

[Bug tree-optimization/66946] Spurious uninitialized warning

2015-07-21 Thread wdijkstr at arm dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66946 --- Comment #4 from Wilco wdijkstr at arm dot com --- (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

[Bug tree-optimization/66946] Spurious uninitialized warning

2015-07-21 Thread wdijkstr at arm dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66946 --- Comment #1 from Wilco wdijkstr at arm dot com --- Created attachment 36021 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=36021action=edit minimal example Minimal example which still reports the spurious warning.