public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/103891] clang-13 fails to compile libstdc++'s std::variant<std::vector<int>>: error: attempt to use a deleted function Date: Tue, 11 Jan 2022 13:24:04 +0000 [thread overview] Message-ID: <bug-103891-4-VIixYKtPpx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103891-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103891 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:5b417b35824fb5c15e3ee958cb86436b3409ebea commit r12-6439-g5b417b35824fb5c15e3ee958cb86436b3409ebea Author: Jonathan Wakely <jwakely@redhat.com> Date: Mon Jan 10 17:28:19 2022 +0000 libstdc++: Make std::variant work with Clang in C++20 mode [PR103891] Clang has some bugs with destructors that use constraints to be conditionally trivial, so disable the P2231R1 constexpr changes to std::variant unless the compiler is GCC 12 or later. If/when P2493R0 gets accepted and implemented by G++ we can remove the __GNUC__ check and use __cpp_concepts >= 202002 instead. libstdc++-v3/ChangeLog: PR libstdc++/103891 * include/bits/c++config (_GLIBCXX_HAVE_COND_TRIVIAL_SPECIAL_MEMBERS): Define. * include/std/variant (__cpp_lib_variant): Only define C++20 value when the compiler is known to support conditionally trivial destructors. * include/std/version (__cpp_lib_variant): Likewise.
next prev parent reply other threads:[~2022-01-11 13:24 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-02 21:40 [Bug libstdc++/103891] New: " slyfox at gcc dot gnu.org 2022-01-02 21:59 ` [Bug libstdc++/103891] " pinskia at gcc dot gnu.org 2022-01-03 15:55 ` ppalka at gcc dot gnu.org 2022-01-04 10:07 ` redi at gcc dot gnu.org 2022-01-04 10:17 ` redi at gcc dot gnu.org 2022-01-09 9:10 ` slyfox at gcc dot gnu.org 2022-01-11 13:24 ` cvs-commit at gcc dot gnu.org [this message] 2022-01-11 13:32 ` redi at gcc dot gnu.org 2022-01-11 16:27 ` slyfox at gcc dot gnu.org 2022-02-14 13:06 ` cvs-commit 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-103891-4-VIixYKtPpx@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: linkBe 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).