public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "martin at martin dot st" <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, 14 Jun 2024 16:10:01 +0000 [thread overview]
Message-ID: <bug-110572-4-GcNQiHR8bH@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 #14 from Martin Storsjö <martin at martin dot st> ---
(In reply to GCC Commits from comment #13)
> The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:
>
> https://gcc.gnu.org/g:6af8d8e618ed27dae3432c96484de4360bd893ab
>
> commit r15-1342-g6af8d8e618ed27dae3432c96484de4360bd893ab
> Author: Jonathan Wakely <jwakely@redhat.com>
> Date: Tue Jun 11 15:52:30 2024 +0100
>
> libstdc++: Make std::type_info::operator== always_inline for C++23
> [PR110572]
Is this enough to fix the issue with Clang, or should I still look into making
Clang predefine __GXX_TYPEINFO_EQUALITY_INLINE=0 for mingw targets? (Even if it
works, it's admittedly not very pretty to rely on "#if !FOO" for an undefined
FOO.)
next prev parent reply other threads:[~2024-06-14 16:10 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
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 [this message]
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-GcNQiHR8bH@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).