public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104539] Failed to inline a very simple template function when it's explicit instantiated.
Date: Thu, 17 Feb 2022 05:11:23 +0000 [thread overview]
Message-ID: <bug-104539-4-M7JmzUdZ0o@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104539-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104539
--- Comment #3 from Jason Merrill <jason at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #2)
> the explicit instantiation lacks COMDAT (but has comdat_group) and it
> has forced_by_abi.
>
> I'm not sure the C++ standard calls out any semantic difference for
> explicit vs. implicit instantiations but maybe the Itanium ABI does.
The ABI says nothing about explicit vs. implicit instantiations.
mark_decl_instantiated cleared DECL_COMDAT to fix PR10968, where we failed to
emit an explicit instantiation. But that was before mark_needed; now that we
have that, I'd think it makes sense to have DECL_COMDAT set on explicit
instantiations just like implicit ones.
next prev parent reply other threads:[~2022-02-17 5:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 4:34 [Bug tree-optimization/104539] New: " cassio.neri at gmail dot com
2022-02-15 4:35 ` [Bug tree-optimization/104539] " cassio.neri at gmail dot com
2022-02-15 8:13 ` [Bug c++/104539] " rguenth at gcc dot gnu.org
2022-02-17 5:11 ` jason at gcc dot gnu.org [this message]
2022-02-17 18:29 ` jason at gcc dot gnu.org
2022-02-17 22:51 ` cvs-commit at gcc dot gnu.org
2022-02-17 22:52 ` jason at gcc dot gnu.org
2024-03-18 7:08 ` pinskia 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-104539-4-M7JmzUdZ0o@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).