[Bug analyzer/99042] Another false -Wanalyzer-malloc-leak on code path involving unknown function call

2021-02-10 Thread antonio.chirizzi at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99042 --- Comment #2 from Antonio Chirizzi --- Hi David, just curious of what you mean with "unknown function". Is it something that has not been declared or is not known to the compiler up to that point? Thanks, -Antonio

[Bug analyzer/99044] New: use-after-free false positive

2021-02-09 Thread antonio.chirizzi at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99044 Bug ID: 99044 Summary: use-after-free false positive Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: analyzer A

[Bug analyzer/99042] New: file-leak is wrong

2021-02-09 Thread antonio.chirizzi at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99042 Bug ID: 99042 Summary: file-leak is wrong Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: analyzer Assignee: dm

[Bug analyzer/99028] New: diagnostic path is too verbose

2021-02-09 Thread antonio.chirizzi at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99028 Bug ID: 99028 Summary: diagnostic path is too verbose Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: analyzer