https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121928
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #7 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
I was able to reproduce this on aarch64-unknown-linux-gnu (cfarm426).
The failures here seem to be due to -Wanalyzer-too-complex firing.
The intent of that test is to verify that
-fanalyzer-show-events-in-system-headers works as expected, not that the
analyzer correctly handles all of the C++ stdlib, which isn't realistic for GCC
16 (should this really be a P1?)
So I'm testing a fix that simply adds -Wno-analyzer-too-complex to the failing
tests; with that, I get:
# of expected passes 1016
# of expected failures 13
# of unsupported tests 23
on aarch64-unknown-linux-gnu
with
make check-g++ RUNTESTFLAGS="-v -v analyzer.exp=*.C"
