[Bug middle-end/87209] Wuninitialized or Wmaybe-uninitialized doesn't warn when malloc's return value is used without being initialized

2020-08-11 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87209 Martin Sebor changed: What|Removed |Added Known to fail||10.2.0, 9.2.0 Target Milestone|---

[Bug middle-end/87209] Wuninitialized or Wmaybe-uninitialized doesn't warn when malloc's return value is used without being initialized

2018-09-15 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87209 --- Comment #3 from Martin Sebor --- (As suggested in bug 87315) besides issuing a warning it would be safer to do what Clang does in cases like this and either replace the code with a trap, or simply eliminate the access (and the malloc call)

[Bug middle-end/87209] Wuninitialized or Wmaybe-uninitialized doesn't warn when malloc's return value is used without being initialized

2018-09-15 Thread manu at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87209 Manuel López-Ibáñez changed: What|Removed |Added CC||msebor at gcc dot gnu.org ---

[Bug middle-end/87209] Wuninitialized or Wmaybe-uninitialized doesn't warn when malloc's return value is used without being initialized

2018-09-04 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87209 Richard Biener changed: What|Removed |Added Keywords||alias, missed-optimization