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++/96840] [11 Regression] Recursive substitution in constrained commutative operator Date: Fri, 18 Dec 2020 03:36:10 +0000 [thread overview] Message-ID: <bug-96840-4-nWsSN6GFFR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96840-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96840 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>: https://gcc.gnu.org/g:79f57d5cb070bb02ea0a34b5f42658d6659b19a8 commit r11-6245-g79f57d5cb070bb02ea0a34b5f42658d6659b19a8 Author: Patrick Palka <ppalka@redhat.com> Date: Thu Dec 17 22:18:07 2020 -0500 c++: Diagnose self-recursive satisfaction This patch further extends the satisfaction_cache class to diagnose self-recursive satisfaction. gcc/cp/ChangeLog: * constraint.cc (sat_entry::evaluating): New member. (satisfaction_cache::get): If entry->evaluating, diagnose self-recursive satisfaction. Otherwise, set entry->evaluating if we're not reusing a cached satisfaction result. (satisfaction_cache::save): Clear entry->evaluating. (satisfy_atom): Set up diagnosing_failed_constraint before the first call to get(). gcc/testsuite/ChangeLog: PR c++/96840 * g++.dg/cpp2a/concepts-pr88395.C: Adjust to expect the self-recursive satisfaction to get directly diagnosed. * g++.dg/cpp2a/concepts-recursive-sat2.C: Likewise. * g++.dg/cpp2a/concepts-recursive-sat4.C: New test.
next prev parent reply other threads:[~2020-12-18 3:36 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-29 0:29 [Bug c++/96840] New: " johelegp at gmail dot com 2020-08-31 6:31 ` [Bug c++/96840] [11 Regression] " rguenth at gcc dot gnu.org 2020-09-28 15:33 ` ppalka at gcc dot gnu.org 2020-10-16 12:05 ` rguenth at gcc dot gnu.org 2020-12-18 3:36 ` cvs-commit at gcc dot gnu.org [this message] 2021-02-01 17:58 ` ppalka at gcc dot gnu.org 2021-12-30 14:06 ` johelegp at gmail dot com 2021-12-30 14:23 ` johelegp at gmail dot com
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-96840-4-nWsSN6GFFR@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).