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++/107179] [11/12/13 Regression] requires-expression gives hard error for inaccessible constructor Date: Thu, 03 Nov 2022 19:36:01 +0000 [thread overview] Message-ID: <bug-107179-4-wBfZHMtKQF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107179-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107179 --- 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:40c34beef620ed13c4113c893ed4335ccc1b8f92 commit r13-3641-g40c34beef620ed13c4113c893ed4335ccc1b8f92 Author: Patrick Palka <ppalka@redhat.com> Date: Thu Nov 3 15:35:18 2022 -0400 c++: requires-expr and access checking [PR107179] Like during satisfaction, we also need to avoid deferring access checks during substitution of a requires-expr because the outcome of an access check can determine the value of the requires-expr. Otherwise (in deferred access checking contexts such as within a base-clause), the requires-expr may evaluate to the wrong result, and along the way a failed access check may leak out from it into a non-SFINAE context and cause a hard error (as in the below testcase). PR c++/107179 gcc/cp/ChangeLog: * constraint.cc (tsubst_requires_expr): Make sure we're not deferring access checks. gcc/testsuite/ChangeLog: * g++.dg/cpp2a/concepts-requires31.C: New test.
next prev parent reply other threads:[~2022-11-03 19:36 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-07 11:53 [Bug c++/107179] New: " redi at gcc dot gnu.org 2022-10-07 13:19 ` [Bug c++/107179] [11/12/13 Regression] " ppalka at gcc dot gnu.org 2022-10-18 8:34 ` rguenth at gcc dot gnu.org 2022-11-03 19:36 ` cvs-commit at gcc dot gnu.org [this message] 2023-03-07 2:18 ` [Bug c++/107179] [11/12 " cvs-commit at gcc dot gnu.org 2023-05-22 3:12 ` [Bug c++/107179] [11 " cvs-commit at gcc dot gnu.org 2023-05-22 3:14 ` 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-107179-4-wBfZHMtKQF@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).