public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/94314] [10 Regression] Optimizing mismatched new/delete pairs since r10-2106-g6343b6bf3bb83c87
Date: Wed, 25 Mar 2020 11:24:45 +0000	[thread overview]
Message-ID: <bug-94314-4-GmiUQGsG4y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94314-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94314

--- Comment #5 from Marc Glisse <glisse at gcc dot gnu.org> ---
I don't think we need heavy machinery linking new and delete (and if we did I'd
be tempted to store it in some global table rather than in the nodes). The most
important case is the global replacable functions, for which we have a finite
list, and for those a few checks like not matching array with non-array
versions should do. For user overloads with attribute malloc (a gcc extension),
I would go with heuristics like both/neither being class members, being members
of the same class, etc. Although I am not quite sure how doable that is from
the middle-end, how much of that information is still available (I think it is
available in the mangled name, but demangling doesn't seem like a great idea).

  parent reply	other threads:[~2020-03-25 11:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-24 21:59 [Bug c++/94314] New: [10 Regression] Optimizing mismatched new/delete pairs glisse at gcc dot gnu.org
2020-03-24 22:29 ` [Bug c++/94314] " jason at gcc dot gnu.org
2020-03-25  7:55 ` rguenth at gcc dot gnu.org
2020-03-25 10:08 ` [Bug c++/94314] [10 Regression] Optimizing mismatched new/delete pairs since r10-2106-g6343b6bf3bb83c87 marxin at gcc dot gnu.org
2020-03-25 10:44 ` rguenth at gcc dot gnu.org
2020-03-25 11:24 ` glisse at gcc dot gnu.org [this message]
2020-03-27 21:43 ` jason at gcc dot gnu.org
2020-03-30  7:57 ` marxin at gcc dot gnu.org
2020-04-01  7:48 ` rguenth at gcc dot gnu.org
2020-04-08 15:17 ` cvs-commit at gcc dot gnu.org
2020-04-08 15:18 ` marxin at gcc dot gnu.org
2020-04-08 16:02 ` glisse at gcc dot gnu.org
2020-04-08 18:04 ` cvs-commit at gcc dot gnu.org
2020-04-09 13:55 ` marxin at gcc dot gnu.org
2020-04-16 13:40 ` cvs-commit at gcc dot gnu.org
2020-04-16 13:41 ` marxin at gcc dot gnu.org
2020-04-17  7:02 ` 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-94314-4-GmiUQGsG4y@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: link
Be 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).