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++: use current_template_constraints more
Date: Sun, 29 May 2022 15:55:34 -0400	[thread overview]
Message-ID: <1343d72b-590b-dac0-803a-330e2b0bad2b@redhat.com> (raw)
In-Reply-To: <20220527180552.2908794-1-ppalka@redhat.com>

On 5/27/22 14:05, Patrick Palka wrote:
> gcc/cp/ChangeLog:
> 
> 	* decl.cc (grokvardecl): Use current_template_constraints.
> 	(xref_tag): Likewise.
> 	* semantics.cc (finish_template_template_parm): Likewise.

OK.

> ---
>   gcc/cp/decl.cc      | 13 +++----------
>   gcc/cp/semantics.cc |  3 +--
>   2 files changed, 4 insertions(+), 12 deletions(-)
> 
> diff --git a/gcc/cp/decl.cc b/gcc/cp/decl.cc
> index 892e4a4b19b..26428ca7122 100644
> --- a/gcc/cp/decl.cc
> +++ b/gcc/cp/decl.cc
> @@ -10789,9 +10789,7 @@ grokvardecl (tree type,
>     else if (flag_concepts
>   	   && current_template_depth > template_class_depth (scope))
>       {
> -      tree reqs = TEMPLATE_PARMS_CONSTRAINTS (current_template_parms);
> -      tree ci = build_constraints (reqs, NULL_TREE);
> -
> +      tree ci = current_template_constraints ();
>         set_constraints (decl, ci);
>       }
>   
> @@ -15852,13 +15850,8 @@ xref_tag (enum tag_types tag_code, tree name,
>           {
>             /* Check that we aren't trying to overload a class with different
>                constraints.  */
> -          tree constr = NULL_TREE;
> -          if (current_template_parms)
> -            {
> -              tree reqs = TEMPLATE_PARMS_CONSTRAINTS (current_template_parms);
> -              constr = build_constraints (reqs, NULL_TREE);
> -            }
> -	  if (!redeclare_class_template (t, current_template_parms, constr))
> +	  if (!redeclare_class_template (t, current_template_parms,
> +					 current_template_constraints ()))
>   	    return error_mark_node;
>           }
>         else if (!processing_template_decl
> diff --git a/gcc/cp/semantics.cc b/gcc/cp/semantics.cc
> index cd7a2818feb..efdeb9318a7 100644
> --- a/gcc/cp/semantics.cc
> +++ b/gcc/cp/semantics.cc
> @@ -3387,8 +3387,7 @@ finish_template_template_parm (tree aggr, tree identifier)
>   
>     /* Associate the constraints with the underlying declaration,
>        not the template.  */
> -  tree reqs = TEMPLATE_PARMS_CONSTRAINTS (current_template_parms);
> -  tree constr = build_constraints (reqs, NULL_TREE);
> +  tree constr = current_template_constraints ();
>     set_constraints (decl, constr);
>   
>     end_template_decl ();


      reply	other threads:[~2022-05-29 19:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 18:05 Patrick Palka
2022-05-29 19:55 ` 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=1343d72b-590b-dac0-803a-330e2b0bad2b@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).