public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vanyacpp at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/94355] support for C++ new expression Date: Mon, 12 Apr 2021 08:04:42 +0000 [thread overview] Message-ID: <bug-94355-4-yqeF0mDXn1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94355-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94355 --- Comment #7 from Ivan Sorokin <vanyacpp at gmail dot com> --- For me the support for operator new works well for trivially constructible types. For a non-trivially constructible type I got a false positive: struct foo { foo(); }; int main() { delete new foo(); } In function 'int main()': cc1plus: warning: use of possibly-NULL 'operator new(1)' where non-null expected [CWE-690] [-Wanalyzer-possible-null-argument] 'int main()': event 1 | |<source>:5:20: | 5 | delete new foo(); | | ^ | | | | | (1) this call could return NULL | 'int main()': event 2 | |cc1plus: | (2): argument 'this' ('operator new(1)') from (1) could be NULL where non-null expected | <source>:1:14: note: argument 'this' of 'foo::foo()' must be non-null 1 | struct foo { foo(); }; | ^~~ Compiler returned: 0 https://godbolt.org/z/nPff9EGsY Also the error location seems to be wrong. Removing "()" from "delete new foo()" fixes the error location.
next prev parent reply other threads:[~2021-04-12 8:04 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-27 11:36 [Bug analyzer/94355] New: " vanyacpp at gmail dot com 2020-03-27 11:59 ` [Bug analyzer/94355] " redi at gcc dot gnu.org 2020-09-09 21:24 ` cvs-commit at gcc dot gnu.org 2020-09-09 21:44 ` dmalcolm at gcc dot gnu.org 2020-09-09 21:50 ` dmalcolm at gcc dot gnu.org 2020-09-26 1:35 ` cvs-commit at gcc dot gnu.org 2021-04-12 7:46 ` vanyacpp at gmail dot com 2021-04-12 8:04 ` vanyacpp at gmail dot com [this message] 2021-07-22 21:14 ` navarre.gcc.bugs at gmail dot com 2021-07-22 21:35 ` redi at gcc dot gnu.org 2022-11-05 9:21 ` redi at gcc dot gnu.org 2022-11-05 9:28 ` redi at gcc dot gnu.org 2022-11-05 9:59 ` redi at gcc dot gnu.org 2022-11-05 16:44 ` dmalcolm at gcc dot gnu.org 2022-11-05 21:31 ` redi at gcc dot gnu.org 2023-06-29 20:01 ` [Bug analyzer/94355] analyzer " vultkayn at gcc dot gnu.org 2023-09-01 20:06 ` cvs-commit at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-94355-4-yqeF0mDXn1@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).