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++/98486] Variable template specialization doesn't account for primary's constraints
Date: Wed, 06 Oct 2021 14:15:30 +0000	[thread overview]
Message-ID: <bug-98486-4-Qae4j1ZWG5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98486-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98486

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Patrick Palka
<ppalka@gcc.gnu.org>:

https://gcc.gnu.org/g:729cf2ea979f396e706625b1669087d5920b8c2a

commit r11-9081-g729cf2ea979f396e706625b1669087d5920b8c2a
Author: Patrick Palka <ppalka@redhat.com>
Date:   Thu Sep 16 15:03:55 2021 -0400

    c++: constrained variable template issues [PR98486]

    This fixes some issues with constrained variable templates:

      - Constraints aren't checked when explicitly specializing a variable
        template.
      - Constraints aren't attached to a static data member template at
        parse time.
      - Constraints don't get propagated when (partially) instantiating a
        static data member template, so we need to make sure to look up
        constraints using the most general template during satisfaction.

            PR c++/98486

    gcc/cp/ChangeLog:

            * constraint.cc (get_normalized_constraints_from_decl): Always
            look up constraints using the most general template.
            * decl.c (grokdeclarator): Set constraints on a static data
            member template.
            * pt.c (determine_specialization): Check constraints on a
            variable template.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp2a/concepts-var-templ1.C: New test.
            * g++.dg/cpp2a/concepts-var-templ1a.C: New test.
            * g++.dg/cpp2a/concepts-var-templ1b.C: New test.

    (cherry picked from commit 2e2e65a46d2674bed53afd211493876ee2b79453)

  parent reply	other threads:[~2021-10-06 14:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-31  6:57 [Bug c++/98486] New: " johelegp at gmail dot com
2021-07-22 14:08 ` [Bug c++/98486] " redi at gcc dot gnu.org
2021-09-15 18:20 ` ppalka at gcc dot gnu.org
2021-09-16 19:04 ` cvs-commit at gcc dot gnu.org
2021-10-06 14:15 ` cvs-commit at gcc dot gnu.org [this message]
2021-10-06 14:18 ` 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-98486-4-Qae4j1ZWG5@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: 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).