public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: Patrick Palka <ppalka@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] c++: requires-expr substitution and access checking [PR107179]
Date: Thu, 3 Nov 2022 14:54:41 -0400	[thread overview]
Message-ID: <b33f1fe6-2e19-4dd3-e29e-74ee0edfaa08@redhat.com> (raw)
In-Reply-To: <20221103154530.1442773-1-ppalka@redhat.com>

On 11/3/22 11:45, Patrick Palka wrote:
> Like during satisfaction, we need to check access immediately during
> substitution of a requires-expr since the outcome of an access check can
> determine the value of the requires-expr.  And otherwise, in contexts
> where access checking is deferred (such as during substitution into a
> base-clause), a failed access check may leak out from the requires-expr
> into a non-SFINAE context and cause a hard error (as in the testcase
> below).
> 
> Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK for
> trunk?

OK.

> 	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.
> ---
>   gcc/cp/constraint.cc                             |  3 +++
>   gcc/testsuite/g++.dg/cpp2a/concepts-requires31.C | 13 +++++++++++++
>   2 files changed, 16 insertions(+)
>   create mode 100644 gcc/testsuite/g++.dg/cpp2a/concepts-requires31.C
> 
> diff --git a/gcc/cp/constraint.cc b/gcc/cp/constraint.cc
> index 5e6a3bcf059..f6ef078171a 100644
> --- a/gcc/cp/constraint.cc
> +++ b/gcc/cp/constraint.cc
> @@ -2252,6 +2252,9 @@ tsubst_requires_expr (tree t, tree args, sat_info info)
>   {
>     local_specialization_stack stack (lss_copy);
>   
> +  /* We need to check access during the substitution.  */
> +  deferring_access_check_sentinel acs (dk_no_deferred);
> +
>     /* A requires-expression is an unevaluated context.  */
>     cp_unevaluated u;
>   
> diff --git a/gcc/testsuite/g++.dg/cpp2a/concepts-requires31.C b/gcc/testsuite/g++.dg/cpp2a/concepts-requires31.C
> new file mode 100644
> index 00000000000..9b7e2a34889
> --- /dev/null
> +++ b/gcc/testsuite/g++.dg/cpp2a/concepts-requires31.C
> @@ -0,0 +1,13 @@
> +// PR c++/107179
> +// { dg-do compile { target c++20 } }
> +
> +template<bool B> struct bool_constant { static constexpr bool value = B; };
> +
> +template<typename T>
> +  struct is_implicitly_default_constructible
> +  : bool_constant<requires { T(); }>
> +  { };
> +
> +struct X { private: X(); };
> +
> +static_assert( !is_implicitly_default_constructible<X>::value );


      reply	other threads:[~2022-11-03 18:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 15:45 Patrick Palka
2022-11-03 18:54 ` Jason Merrill [this message]

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=b33f1fe6-2e19-4dd3-e29e-74ee0edfaa08@redhat.com \
    --to=jason@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ppalka@redhat.com \
    /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: link
Be 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).