https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96395
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |97110
Summary|gcc.dg/analyzer/explode-2.c |Generalize gcc.dg/analyzer
|fails when compiled as C++ |tests to be run with both C
| |and C++
--- Comment #5 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to David Malcolm from comment #3)
> 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 switch statements are handled, so perhaps that fixed it.
>
> That said, there's merit in generalizing the C tests so they run for both C
> and C++, so maybe this bug should track that.
Based on the above, updating summary to:
"Generalize gcc.dg/analyzer tests to be run with both C and C++"
and adding to C++ tracker bug.
(perhaps they should be moved to c-c++-common as part of this)
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97110
[Bug 97110] [meta-bug] tracker bug for supporting C++ in -fanalyzer
