public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: Richard Biener <rguenther@suse.de>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] tree-optimization/97151 - improve PTA for C++ operator delete
Date: Wed, 23 Sep 2020 13:53:18 -0400	[thread overview]
Message-ID: <5878a705-6101-d7ac-fe11-13664a53b220@redhat.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.2009231013440.11491@elmra>

On 9/23/20 4:14 AM, Richard Biener wrote:
> C++ operator delete, when DECL_IS_REPLACEABLE_OPERATOR_DELETE_P,
> does not cause the deleted object to be escaped.  It also has no
> other interesting side-effects for PTA so skip it like we do
> for BUILT_IN_FREE.

Hmm, this is true of the default implementation, but since the function 
is replaceable, we don't know what a user definition might do with the 
pointer.

> Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed.
> 
> Richard.
> 
> 2020-09-23  Richard Biener  <rguenther@suse.de>
> 
> 	PR tree-optimization/97151
> 	* tree-ssa-structalias.c (find_func_aliases_for_call):
> 	DECL_IS_REPLACEABLE_OPERATOR_DELETE_P has no effect on
> 	arguments.
> 
> 	* g++.dg/cpp1y/new1.C: Adjust for two more handled transforms.
> ---
>   gcc/testsuite/g++.dg/cpp1y/new1.C | 4 ++--
>   gcc/tree-ssa-structalias.c        | 2 ++
>   2 files changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/gcc/testsuite/g++.dg/cpp1y/new1.C b/gcc/testsuite/g++.dg/cpp1y/new1.C
> index aa5f647d535..fec0088cb40 100644
> --- a/gcc/testsuite/g++.dg/cpp1y/new1.C
> +++ b/gcc/testsuite/g++.dg/cpp1y/new1.C
> @@ -69,5 +69,5 @@ test_unused() {
>     delete p;
>   }
>   
> -/* { dg-final { scan-tree-dump-times "Deleting : operator delete" 5 "cddce1"} } */
> -/* { dg-final { scan-tree-dump-times "Deleting : _\\d+ = operator new" 7 "cddce1"} } */
> +/* { dg-final { scan-tree-dump-times "Deleting : operator delete" 6 "cddce1"} } */
> +/* { dg-final { scan-tree-dump-times "Deleting : _\\d+ = operator new" 8 "cddce1"} } */
> diff --git a/gcc/tree-ssa-structalias.c b/gcc/tree-ssa-structalias.c
> index 44fe52e0f65..f676bf91e95 100644
> --- a/gcc/tree-ssa-structalias.c
> +++ b/gcc/tree-ssa-structalias.c
> @@ -4857,6 +4857,8 @@ find_func_aliases_for_call (struct function *fn, gcall *t)
>   	 point for reachable memory of their arguments.  */
>         else if (flags & (ECF_PURE|ECF_LOOPING_CONST_OR_PURE))
>   	handle_pure_call (t, &rhsc);
> +      else if (fndecl && DECL_IS_REPLACEABLE_OPERATOR_DELETE_P (fndecl))
> +	;
>         else
>   	handle_rhs_call (t, &rhsc);
>         if (gimple_call_lhs (t))
> 


  reply	other threads:[~2020-09-23 17:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-23  8:14 Richard Biener
2020-09-23 17:53 ` Jason Merrill [this message]
2020-09-23 18:42   ` Richard Biener
2020-09-23 20:48     ` Jason Merrill
2020-09-24  7:43       ` Richard Biener
2020-09-24 19:37         ` Jason Merrill
2020-09-25  6:30           ` Richard Biener
2020-09-25 20:04             ` Jason Merrill
2020-09-28  7:56               ` Richard Biener
2020-09-28 19:09                 ` Jason Merrill
2020-09-30 15:36                   ` Jason Merrill
2020-10-01  9:26                     ` Richard Biener
2020-10-02  3:27                       ` Jason Merrill
2020-10-02  9:17                         ` Richard Biener

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=5878a705-6101-d7ac-fe11-13664a53b220@redhat.com \
    --to=jason@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rguenther@suse.de \
    /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).