https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108535
--- Comment #2 from Jamie Bainbridge ---
Ah, I've misunderstood how the analyzer works, my apologies.
(In reply to David Malcolm from comment #1)
> It sounds like what you really want is for GCC -fanalyzer to be faster on
> this particular
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108535
Bug ID: 108535
Summary: RFE: analyzer to allow ifdef inclusion/exclusion like
cppcheck -D/-U
Product: gcc
Version: 12.1.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108045
Bug ID: 108045
Summary: analyzer: false positive memory leak
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: analyzer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107573
--- Comment #1 from Jamie Bainbridge ---
Thanks for logging this!
(In reply to David Malcolm from comment #0)
> - complain about NULL passed as the string to the first call of strtok
> reached from entry to "main" (I don't think there's a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107566
--- Comment #3 from Jamie Bainbridge ---
Compiler Explorer are still tracking the old "devel/analyzer" branch.
Logged an Issue for them to consider update options:
[BUG]: GCC static analysis branch is outdated/obsolete #4256
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107566
--- Comment #2 from Jamie Bainbridge ---
Thanks for the quick response!
I guess Compiler Explorer doesn't enable static analysis on its "trunk"
compiler, and I also see now its "static analysis" branch is back at gcc-10.
I'll see what I can do
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107566
Bug ID: 107566
Summary: array out of bounds not detected
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: analyzer
