[Bug c++/86176] Wnull-dereference warning disappears with a call to std::cout on the line after

2018-06-18 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86176 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug c++/86176] Wnull-dereference warning disappears with a call to std::cout on the line after

2018-06-18 Thread jg at jguk dot org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86176 --- Comment #2 from Jonny Grant --- I wonder, is there a way to configure GCC to perform in a way similar to static analyser? GCC warnings are very useful.

[Bug c++/86176] Wnull-dereference warning disappears with a call to std::cout on the line after

2018-06-18 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86176 --- Comment #3 from Jonathan Wakely --- No, because GCC is not a static analyser.

[Bug c++/86176] Wnull-dereference warning disappears with a call to std::cout on the line after

2019-12-21 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86176 --- Comment #6 from Eric Gallager --- (In reply to Jonathan Wakely from comment #3) > No, because GCC is not a static analyser. It'll have one once David Malcolm's static analyzer branch is merged

[Bug c++/86176] Wnull-dereference warning disappears with a call to std::cout on the line after

2018-12-17 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86176 Eric Gallager changed: What|Removed |Added CC||msebor at gcc dot gnu.org --- Comment #4

[Bug c++/86176] Wnull-dereference warning disappears with a call to std::cout on the line after

2018-12-17 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86176 --- Comment #5 from Martin Sebor --- I think the question in comment #2 is whether it's possible to get the full benefit of the latter kind of warnings without relying on the optimizations being performed that they depend on. There is currently