[Bug analyzer/126830] New: Tracker bug for -fanalyzer false positives seen in August 2026 OpenScanHub mass scan
"dmalcolm at gcc dot gnu.org via Gcc-bugs" <[email protected]>
| Newsgroups | gmane.comp.gcc.bugs |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=126830
Bug ID: 126830
Summary: Tracker bug for -fanalyzer false positives seen in
August 2026 OpenScanHub mass scan
Product: gcc
Version: 17.0
Status: UNCONFIRMED
Keywords: meta-bug
Severity: normal
Priority: P3
Component: analyzer
Assignee: dmalcolm at gcc dot gnu.org
Reporter: dmalcolm at gcc dot gnu.org
Target Milestone: ---
GCC's analyzer was used by Fedora as part of a scan of Fedora 45 Critical Path
Packages in August 2026:
https://lists.fedoraproject.org/archives/list/[email protected]/thread/YBJ4C2PTK6N3LBQVAOM7SPPHXHAUW6SF/
The results from -fanalyzer were run through Opus 4.6 (1M context) which
identified 15401 of the gcc -fanalyzer reports as false positives, across 496
Fedora packages.
I've had Claude Code look at these, and it's come up with a prioritized
collection of root cause themes, along with reproducers for representative
examples of each root cause.
I intend to file bugs for the various root causes - I'll use this as a tracker
bug to help organize the results.