https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107060
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |99390
--- Comment #5 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
The real issue here is that -fanalyzer-call-summaries is off by default (due to
being buggy). Poring over the dumps shows that without trying to summarize the
effects of calls, the analyzer is brute-forcing the exploration of the call
graph, leading to an explosion of deep paths, expensively achieving very poor
coverage.
Enabling -fanalyzer-call-summaries speeds things up from ~10 minutes to ~1m20s
(7.5x), but makes it emit lots of -Wanalyzer-use-of-uninitialized-value false
positives. Am about to file a bug about that...
Sorry about this; I'd recommend disabling -fanalyzer on Emacs until it's
reasonable to enable -fanalyzer-call-summaries on it.
The dumps show some other issues, like the analyzer seems to be creating lots
of regions for tracking "alloca" (~45000 of them in one dump), so I may need to
also fix how alloca is handled.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99390
[Bug 99390] [meta-bug] tracker bug for call summaries in -fanalyzer
