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++, v3: Retry the aliasing of base/complete cdtor optimization at import_export_decl time [PR113208]
Date: Wed, 24 Apr 2024 20:43:46 -0400 [thread overview]
Message-ID: <5f6569bc-8d94-434c-b66d-137c8e7f5e64@redhat.com> (raw)
In-Reply-To: <ZimMH1d8gWSthdGz@tucnak>
On 4/24/24 15:47, Jakub Jelinek wrote:
> On Wed, Apr 24, 2024 at 06:39:33PM -0400, Jason Merrill wrote:
>>> --- gcc/cp/decl2.cc.jj 2024-04-23 14:49:41.933186265 +0200
>>> +++ gcc/cp/decl2.cc 2024-04-24 15:17:09.043625729 +0200
>>> @@ -3314,7 +3314,16 @@ tentative_decl_linkage (tree decl)
>>> to mark the functions at this point. */
>>> if (DECL_DECLARED_INLINE_P (decl)
>>> && (!DECL_IMPLICIT_INSTANTIATION (decl)
>>> - || DECL_DEFAULTED_FN (decl)))
>>> + || DECL_DEFAULTED_FN (decl)
>>> + /* For implicit instantiations of cdtors,
>>> + if import_export_decl would use comdat linkage,
>>> + make sure to use it right away, so that maybe_clone_body
>>> + can use aliases. See PR113208. */
>>> + || (DECL_MAYBE_IN_CHARGE_CDTOR_P (decl)
>>> + && (flag_implicit_templates
>>> + || flag_implicit_inline_templates)
>>> + && flag_weak
>>> + && TARGET_SUPPORTS_ALIASES)))
>>
>> It seems wrong to set DECL_INTERFACE_KNOWN for cdtors that might get an
>> explicit instantiation later, and likewise for comdat_linkage when
>> !flag_weak; instead of adding this condition to the if, how about adding an
>> else like
>>
>>> else if (DECL_MAYBE_IN_CHARGE_CDTOR_P (decl))
>>> /* For implicit instantiations of cdtors,
>>> if import_export_decl would use comdat linkage,
>>> make sure to use it right away, so that maybe_clone_body
>>> can use aliases. See PR113208. */
>>> maybe_make_one_only (decl);
>>
>> ?
>
> Then can_alias_cdtor would return false, because it ends with:
> /* 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))));
> Should we change that DECL_INTERFACE_KNOWN (fn) in there to
> (DECL_INTERFACE_KNOWN (fn) || something) then and what that
> something should be? HAVE_COMDAT_GROUP && DECL_ONE_ONLY (fn)?
Yes, I think reorganize to
((DECL_INTERFACE_KNOWN (fn) && !DECL_WEAK (fn) && !DECL_ONE_ONLY (fn))
|| (HAVE_COMDAT_GROUP && DECL_ONE_ONLY (fn))
Jason
next prev parent reply other threads:[~2024-04-25 0:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 7:42 [PATCH] c++: " 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 [this message]
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
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=5f6569bc-8d94-434c-b66d-137c8e7f5e64@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).