https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95043
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |UNCONFIRMED
Ever confirmed|1 |0
--- Comment #2 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
I can reproduce a warning with the preprocessed source with gcc 10 at -O1 and
above; stripping out the line-markers with:
perl -pi -e 's/^#.*\n//g;' idea.ii
I get:
https://godbolt.org/z/qxehzM
which shows a diagnostic, where (I think) m_array is NULL from
m_fallbackAllocator.allocate, which looks like a valid warning.
With gcc 11, -Wanalyzer-too-complex shows that the analyzer is hitting the
complexity limit and bailing out, without emitting the diagnostic.
