[Bug analyzer/96395] gcc.dg/analyzer/explode-2.c fails when compiled as C++

2021-02-12 Thread dmalcolm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96395 --- Comment #4 from David Malcolm --- (In reply to David Malcolm from comment #3) > FWIW, I'm not able to reproduce this issue with trunk. Note that > g:fd111c419d146ee47c7df9a36a535e8d843d4802 fixed a state-explosion bug in > how switch stateme

[Bug analyzer/96395] gcc.dg/analyzer/explode-2.c fails when compiled as C++

2021-02-12 Thread dmalcolm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96395 --- Comment #3 from David Malcolm --- Sandra: what is the status of your loop unification changes? FWIW, I'm not able to reproduce this issue with trunk. Note that g:fd111c419d146ee47c7df9a36a535e8d843d4802 fixed a state-explosion bug in how sw

[Bug analyzer/96395] gcc.dg/analyzer/explode-2.c fails when compiled as C++

2020-07-31 Thread sandra at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96395 sandra at gcc dot gnu.org changed: What|Removed |Added CC||sandra at gcc dot gnu.org ---

[Bug analyzer/96395] gcc.dg/analyzer/explode-2.c fails when compiled as C++

2020-07-31 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96395 --- Comment #1 from David Malcolm --- Thanks for filing this. FWIW I've spent the last 4 months rewriting the state-tracking heart of the analyzer, with a patch kit I hope to land next month. Along with many other changes, explode-2.c changes b