public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/110572] ld.lld: error: duplicate symbol: std::type_info::operator==(std::type_info const&) const
Date: Fri, 31 May 2024 13:44:19 +0000	[thread overview]
Message-ID: <bug-110572-4-YPdxbQSCad@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110572-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This is the fix I'm suggesting:

--- a/libstdc++-v3/libsupc++/typeinfo
+++ b/libstdc++-v3/libsupc++/typeinfo
@@ -188,6 +188,9 @@ namespace std
 #endif

 #if __GXX_TYPEINFO_EQUALITY_INLINE || __cplusplus > 202002L
+# if ! __GXX_TYPEINFO_EQUALITY_INLINE
+  [[__gnu__::__always_inline__]]
+# endif
   _GLIBCXX23_CONSTEXPR inline bool
   type_info::operator==(const type_info& __arg) const _GLIBCXX_NOEXCEPT
   {

  parent reply	other threads:[~2024-05-31 13:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06 11:07 [Bug libstdc++/110572] New: " arndtthomas at gmx dot de
2023-07-06 11:34 ` [Bug libstdc++/110572] " redi at gcc dot gnu.org
2023-07-06 13:11 ` redi at gcc dot gnu.org
2023-07-06 13:14 ` redi at gcc dot gnu.org
2023-07-10  8:14 ` arndtthomas at gmx dot de
2023-09-01 21:30 ` peter0x44 at disroot dot org
2024-05-31 13:23 ` redi at gcc dot gnu.org
2024-05-31 13:44 ` redi at gcc dot gnu.org [this message]
2024-05-31 14:14 ` peter0x44 at disroot dot org
2024-05-31 14:17 ` redi at gcc dot gnu.org
2024-05-31 14:18 ` redi at gcc dot gnu.org
2024-05-31 14:29 ` redi at gcc dot gnu.org
2024-06-03 11:49 ` martin at martin dot st
2024-06-14 14:54 ` cvs-commit at gcc dot gnu.org
2024-06-14 16:10 ` martin at martin dot st
2024-06-14 16:33 ` redi at gcc dot gnu.org
2024-06-20  9:13 ` rguenth 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-110572-4-YPdxbQSCad@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).