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++/103714] [11/12 Regression] name lookup in requires-clause finds wrong thing
Date: Sun, 19 Dec 2021 17:10:32 +0000	[thread overview]
Message-ID: <bug-103714-4-0SQFRmlRQe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103714-4@http.gcc.gnu.org/bugzilla/>

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

--- 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:30c286aa9377850c64aa35f5845a59d321a44be0

commit r12-6063-g30c286aa9377850c64aa35f5845a59d321a44be0
Author: Patrick Palka <ppalka@redhat.com>
Date:   Sun Dec 19 12:10:16 2021 -0500

    c++: local_specializations and recursive constrained fn [PR103714]

    Here during constraint checking for the inner call to A<0>::f<0>,
    substitution into the PARM_DECL d in the atomic constraint yields the
    wrong local specialization because local_specializations at this point
    is nonempty, and contains specializations for the caller A<0>::f<1>.

    This patch makes us call push_to_top_level during satisfaction, which'll
    temporarily clear local_specializations for us.

            PR c++/103714

    gcc/cp/ChangeLog:

            * constraint.cc (satisfy_declaration_constraints): Do
            push_to_top_level and pop_from_top_level around the call to
            satisfy_normalized_constraints.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp2a/concepts-uneval5.C: New test.

  parent reply	other threads:[~2021-12-19 17:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14 17:16 [Bug c++/103714] New: " redi at gcc dot gnu.org
2021-12-14 17:18 ` [Bug c++/103714] " redi at gcc dot gnu.org
2021-12-14 22:26 ` ppalka at gcc dot gnu.org
2021-12-19 17:10 ` cvs-commit at gcc dot gnu.org [this message]
2021-12-19 19:10 ` cvs-commit at gcc dot gnu.org
2021-12-19 19:10 ` 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-103714-4-0SQFRmlRQe@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).