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++/96164] Constraints and explicit template instantiation
Date: Thu, 30 Jul 2020 02:15:12 +0000	[thread overview]
Message-ID: <bug-96164-4-NzVimbXVSC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96164-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 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:dc3d1e181445fafbbd146eb355a750c41c338794

commit r11-2417-gdc3d1e181445fafbbd146eb355a750c41c338794
Author: Patrick Palka <ppalka@redhat.com>
Date:   Wed Jul 29 22:06:33 2020 -0400

    c++: constraints and explicit instantiation [PR96164]

    When considering to instantiate a member of a class template as part of
    an explicit instantiation of the class template, we need to first check
    the member's constraints before proceeding with the instantiation of the
    member.

    gcc/cp/ChangeLog:

            PR c++/96164
            * constraint.cc (constraints_satisfied_p): Return true if
            !flags_concepts.
            * pt.c (do_type_instantiation): Update a paragraph taken from
            [temp.explicit] to reflect the latest specification.  Don't
            instantiate a member with unsatisfied constraints.

    gcc/testsuite/ChangeLog:

            PR c++/96164
            * g++.dg/cpp2a/concepts-explicit-inst5.C: New test.

  parent reply	other threads:[~2020-07-30  2:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-11  9:01 [Bug c++/96164] New: " jaahans2 at gmail dot com
2020-07-11  9:04 ` [Bug c++/96164] " jaahans2 at gmail dot com
2020-07-11 16:46 ` ppalka at gcc dot gnu.org
2020-07-11 16:47 ` ppalka at gcc dot gnu.org
2020-07-30  2:15 ` cvs-commit at gcc dot gnu.org [this message]
2020-08-11  2:36 ` cvs-commit at gcc dot gnu.org
2020-08-11  2:39 ` ppalka at gcc dot gnu.org
2021-11-11 22:25 ` pinskia at gcc dot gnu.org
2023-03-15 13:25 ` 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-96164-4-NzVimbXVSC@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).