public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Jonathan Wakely <jwakely@redhat.com>, Jan Hubicka <jh@suse.cz>,
	gcc-patches@gcc.gnu.org, Richard Biener <rguenther@suse.de>,
	Patrick Palka <ppalka@redhat.com>
Subject: Re: [PATCH] c++: Optimize in maybe_clone_body aliases even when not at_eof [PR113208]
Date: Fri, 10 May 2024 15:59:25 -0400	[thread overview]
Message-ID: <c6a70968-23e2-4d61-a2f3-caf9450d2df8@redhat.com> (raw)
In-Reply-To: <Zj0T0KbGM9iIZy/+@tucnak>

On 5/9/24 14:20, Jakub Jelinek wrote:
> On Thu, Apr 25, 2024 at 11:30:48AM -0400, Jason Merrill wrote:
>> Hmm, maybe maybe_clone_body shouldn't clear DECL_SAVED_TREE for aliases, but
>> rather set it to some stub like void_node?
>>
>> Though with all these changes, it's probably better to go with your first
>> patch for GCC 14 and delay this approach to 15.  Your v1 patch is OK for 14.
> 
> Ok, here is an updated patch, which sets DECL_SAVED_TREE to void_node for
> the aliases together with reversion of the earlier committed patch.
> 
> Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
> 
> 2024-05-09  Jakub Jelinek  <jakub@redhat.com>
> 	    Jason Merrill  <jason@redhat.com>
> 
> 	PR lto/113208
> 	* cp-tree.h (maybe_optimize_cdtor): Remove.
> 	* decl2.cc (tentative_decl_linkage): Call maybe_make_one_only
> 	for implicit instantiations of maybe in charge ctors/dtors
> 	declared inline.
> 	(import_export_decl): Don't call maybe_optimize_cdtor.
> 	(c_parse_final_cleanups): Formatting fixes.
> 	* optimize.cc (can_alias_cdtor): Adjust condition, for
> 	HAVE_COMDAT_GROUP && DECL_ONE_ONLY && DECL_WEAK return true even
> 	if not DECL_INTERFACE_KNOWN.

> --- gcc/cp/optimize.cc.jj	2024-04-25 20:33:30.771858912 +0200
> +++ gcc/cp/optimize.cc	2024-05-09 17:10:23.920478922 +0200
> @@ -220,10 +220,8 @@ can_alias_cdtor (tree fn)
>     gcc_assert (DECL_MAYBE_IN_CHARGE_CDTOR_P (fn));
>     /* Don't use aliases for weak/linkonce definitions unless we can put both
>        symbols in the same COMDAT group.  */
> -  return (DECL_INTERFACE_KNOWN (fn)
> -	  && (SUPPORTS_ONE_ONLY || !DECL_WEAK (fn))
> -	  && (!DECL_ONE_ONLY (fn)
> -	      || (HAVE_COMDAT_GROUP && DECL_WEAK (fn))));
> +  return (DECL_WEAK (fn) ? (HAVE_COMDAT_GROUP && DECL_ONE_ONLY (fn))
> +			 : (DECL_INTERFACE_KNOWN (fn) && !DECL_ONE_ONLY (fn)));

Hmm, would

(DECL_ONE_ONLY (fn) ? HAVE_COMDAT_GROUP
  : (DECL_INTERFACE_KNOWN (fn) && !DECL_WEAK (fn)))

make sense instead?  I don't think DECL_WEAK is necessary for COMDAT.

Jason


  parent reply	other threads:[~2024-05-10 19:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-17  7:42 [PATCH] c++: Retry the aliasing of base/complete cdtor optimization at import_export_decl time [PR113208] Jakub Jelinek
2024-04-17  9:04 ` Jan Hubicka
2024-04-17 12:32   ` Jakub Jelinek
2024-04-17 13:26     ` Jan Hubicka
2024-04-17 14:07       ` Jakub Jelinek
2024-04-17 14:34         ` Jan Hubicka
2024-04-17 14:39           ` Jakub Jelinek
2024-04-22 15:42 ` [PATCH] c++, v2: " Jakub Jelinek
2024-04-23  3:14   ` Jason Merrill
2024-04-23 16:04     ` Jakub Jelinek
2024-04-24  9:16       ` Jonathan Wakely
2024-04-24 16:16         ` [PATCH] c++, v3: " Jakub Jelinek
2024-04-24 22:39           ` Jason Merrill
2024-04-24 22:47             ` Jakub Jelinek
2024-04-25  0:43               ` Jason Merrill
2024-04-25 12:02                 ` [PATCH] c++, v4: " Jakub Jelinek
2024-04-25 14:22                   ` Jakub Jelinek
2024-04-25 15:30                     ` Jason Merrill
2024-04-25 18:42                       ` [PATCH] c++, v5: " Jakub Jelinek
2024-05-09 18:20                       ` [PATCH] c++: Optimize in maybe_clone_body aliases even when not at_eof [PR113208] Jakub Jelinek
2024-05-09 18:58                         ` Marek Polacek
2024-05-09 19:05                           ` Jakub Jelinek
2024-05-10 19:59                         ` Jason Merrill [this message]
2024-05-13 10:19                           ` Jakub Jelinek
2024-05-14 22:20                             ` Jason Merrill

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=c6a70968-23e2-4d61-a2f3-caf9450d2df8@redhat.com \
    --to=jason@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jh@suse.cz \
    --cc=jwakely@redhat.com \
    --cc=ppalka@redhat.com \
    --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).