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
--- Comment #2 from sandra at gcc dot gnu.org ---
Once my C/C++ loop unification changes are in, this test case will fail when
compiled as C, too. Recording that it fails as C++ already gives you a way to
duplicate the bug meanwhile, independently of my patches, and also gives me an
issue to track the future C testsuite regression introduced by my patches.
It seems like it would be a good idea generally to run analyzer unit tests as
both C and C++, though. This is a pretty simple test case, and yet the
analyzer completely falls over on it, which doesn't fill me with confidence on
how well it would work on any real C++ program, even one that doesn't use
templates or exceptions.
