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 c++/106361] [11/12/13 Regression] Internal compiler error when creating an out-of-line operator==() = default Date: Thu, 21 Jul 2022 21:23:02 +0000 [thread overview] Message-ID: <bug-106361-4-rCAxENglZI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106361-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106361 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:707bc64fbeecf8a10f7aad103534b6999e9d190c commit r12-8607-g707bc64fbeecf8a10f7aad103534b6999e9d190c Author: Jason Merrill <jason@redhat.com> Date: Wed Jul 20 20:00:58 2022 -0400 c++: defaulted friend op== [PR106361] Now non-member functions can be defaulted, so this assert is wrong. move_signature_fn_p already checks for ctor or op=. PR c++/106361 gcc/cp/ChangeLog: * decl.cc (move_fn_p): Remove assert. gcc/testsuite/ChangeLog: * g++.dg/cpp2a/spaceship-eq14.C: New test.
next prev parent reply other threads:[~2022-07-21 21:23 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-19 22:15 [Bug c++/106361] New: " leo at adberg dot com 2022-07-19 22:19 ` [Bug c++/106361] " pinskia at gcc dot gnu.org 2022-07-19 22:21 ` [Bug c++/106361] [11/12/13 Regression] " pinskia at gcc dot gnu.org 2022-07-19 22:22 ` pinskia at gcc dot gnu.org 2022-07-19 22:24 ` leo at adberg dot com 2022-07-19 22:25 ` mpolacek at gcc dot gnu.org 2022-07-19 22:25 ` pinskia at gcc dot gnu.org 2022-07-21 21:21 ` cvs-commit at gcc dot gnu.org 2022-07-21 21:23 ` cvs-commit at gcc dot gnu.org [this message] 2022-07-22 5:40 ` cvs-commit at gcc dot gnu.org 2023-01-06 16:06 ` ppalka 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-106361-4-rCAxENglZI@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).