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++/99846] [11 regression] std::variant comparison operator error for recursive type Date: Thu, 08 Apr 2021 13:46:10 +0000 [thread overview] Message-ID: <bug-99846-4-dviMGEdyJc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99846-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99846 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jason at gcc dot gnu.org --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> --- Preprocessing the attached testcase with GCC 10 (using -std=c++20) and compiling with GCC 11 shows the error. Possibly a compiler bug (or invalid code in the library, which gcc 10 doesn't complain about). It started to fail on trunk with r11-2774 c++: Check satisfaction before non-dep convs. [CWG2369] It's very hard to use concepts to protect a template from hard errors due to unwanted instantiation if constraints aren't checked until after doing all substitution and checking of non-dependent conversions. It was pretty straightforward to insert the satisfaction check into the logic, but I needed to make the 3-parameter version of satisfy_declaration_constraints call push_tinst_level like the 2-parameter version already does. For simplicity, I also made it add any needed outer template arguments from the TEMPLATE_DECL to the args. The testsuite changes are mostly because this change causes unsatisfaction to cause deduction to fail rather than reject the candidate later in overload resolution. gcc/cp/ChangeLog: DR 2369 * cp-tree.h (push_tinst_level, push_tinst_level_loc): Declare. * constraint.cc (satisfy_declaration_constraints): Use add_outermost_template_args and push_tinst_level. * pt.c (add_outermost_template_args): Handle getting a TEMPLATE_DECL as the first argument. (push_tinst_level, push_tinst_level_loc): No longer static. (fn_type_unification): Check satisfaction before non-dependent conversions.
next prev parent reply other threads:[~2021-04-08 13:46 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-31 9:26 [Bug libstdc++/99846] New: " nilsgladitz at gmail dot com 2021-03-31 9:56 ` [Bug libstdc++/99846] " rguenth at gcc dot gnu.org 2021-04-08 13:24 ` rguenth at gcc dot gnu.org 2021-04-08 13:41 ` redi at gcc dot gnu.org 2021-04-08 13:42 ` redi at gcc dot gnu.org 2021-04-08 13:46 ` redi at gcc dot gnu.org [this message] 2021-04-13 14:33 ` redi at gcc dot gnu.org 2021-04-13 14:42 ` redi at gcc dot gnu.org 2021-04-13 15:06 ` ppalka at gcc dot gnu.org 2021-04-13 18:27 ` nilsgladitz at gmail dot com 2021-04-13 20:25 ` redi at gcc dot gnu.org 2021-04-13 20:47 ` redi 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-99846-4-dviMGEdyJc@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).