public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/94355] support for C++ new expression Date: Wed, 09 Sep 2020 21:44:09 +0000 [thread overview] Message-ID: <bug-94355-4-Sj6V5fV94m@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 David Malcolm <dmalcolm at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 Last reconfirmed| |2020-09-09 --- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> --- The above patch is an initial implementation of new/delete support; it works for the simplest cases. As noted in the commit message this patch was mostly about generalizing the sm-malloc.cc code; the implementation of new/delete will no doubt need much further refinement (and beyond that, the analyzer doesn't yet know about vfuncs, exceptions, inheritance, RTTI, etc) Specific things still to be investigated relating to new/delete (if only to add test coverage): * all of the various cases seen at https://en.cppreference.com/w/cpp/memory/new/operator_new * placement new * global and class-specific replacements for operator new/new[] * exceptions vs non-throwing allocators vs -fno-exceptions * verify that ctors/dtors are simulated appropriately for both scalar and vector new/delete Anything else? Note to self: see also https://en.cppreference.com/w/cpp/language/new
next prev parent reply other threads:[~2020-09-09 21:44 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 [this message] 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 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-Sj6V5fV94m@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).