[Bug analyzer/115724] analyzer does not recognise glibc (GNU) extension, non-returning error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115724 --- Comment #3 from Jamie Bainbridge --- Thank you for the speedy response, confirmation, and workaround. I did not think to check if error() was standard or not. Good point. No problems on prioritisation or even disregarding this. When behavi

[Bug analyzer/115724] New: analyzer does not recognise non-returning error()

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115724 Bug ID: 115724 Summary: analyzer does not recognise non-returning error() Product: gcc Version: 15.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component

[Bug analyzer/108535] RFE: analyzer to allow ifdef inclusion/exclusion like cppcheck -D/-U

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 tran

[Bug analyzer/108535] New: RFE: analyzer to allow ifdef inclusion/exclusion like cppcheck -D/-U

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

[Bug analyzer/108045] New: analyzer: false positive memory leak

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

[Bug analyzer/107573] RFE: analyzer handling of strtok

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 guara

[Bug analyzer/107566] array out of bounds not detected

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://github.

[Bug analyzer/107566] array out of bounds not detected

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

[Bug analyzer/107566] New: array out of bounds not detected

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