From: Jason Merrill <jason@redhat.com>
To: Alexandre Oliva <aoliva@redhat.com>, gcc-patches@gcc.gnu.org
Cc: nathan@acm.org
Subject: Re: [PATCH] [PR86747] tsubst friend tpl ctxt before looking it up for dupes
Date: Thu, 06 Dec 2018 01:17:00 -0000 [thread overview]
Message-ID: <2ea1509b-af63-520a-05c1-be94f5305b28@redhat.com> (raw)
In-Reply-To: <or5zwwk60e.fsf@lxoliva.fsfla.org>
On 11/16/18 5:32 PM, Alexandre Oliva wrote:
> When a member template is redeclared as a friend, we enter the context
> of the member before looking it up, and then we check that the decls
> are compatible. However, when the member template references template
> types of the enclosing context, say an enclosing template class, the
> compare fails because the friend decl is already tsubsted, whereas the
> looked up name isn't.
>
> The problem is that the enclosing context is taken from the friend
> declaration before tsubsting it, so we look up in the context of the
> generic template instead of that of the tsubsted one we're
> specializing. The solution is to tsubst the enclosing context when
> it's a non-namespace scope.
>
> Regstrapped on i686- and x86_64-linux-gnu. Ok to install?
OK.
>
>
> for gcc/cp/ChangeLog
>
> PR c++/86747
> * pt.c (tsubst_friend_class): Enter tsubsted class context.
>
> for gcc/testsuite/ChangeLog
>
> PR c++/86747
> * g++.dg/pr86747.C: New.
> ---
> gcc/cp/pt.c | 5 ++++-
> gcc/testsuite/g++.dg/pr86747.C | 8 ++++++++
> 2 files changed, 12 insertions(+), 1 deletion(-)
> create mode 100644 gcc/testsuite/g++.dg/pr86747.C
>
> diff --git a/gcc/cp/pt.c b/gcc/cp/pt.c
> index 83d0a74b209f..82c8019431b8 100644
> --- a/gcc/cp/pt.c
> +++ b/gcc/cp/pt.c
> @@ -10568,7 +10568,10 @@ tsubst_friend_class (tree friend_tmpl, tree args)
> if (TREE_CODE (context) == NAMESPACE_DECL)
> push_nested_namespace (context);
> else
> - push_nested_class (context);
> + {
> + context = tsubst (context, args, tf_error, NULL_TREE);
> + push_nested_class (context);
> + }
>
> tmpl = lookup_name_real (DECL_NAME (friend_tmpl), /*prefer_type=*/false,
> /*non_class=*/false, /*block_p=*/false,
> diff --git a/gcc/testsuite/g++.dg/pr86747.C b/gcc/testsuite/g++.dg/pr86747.C
> new file mode 100644
> index 000000000000..5b0a0bb95146
> --- /dev/null
> +++ b/gcc/testsuite/g++.dg/pr86747.C
> @@ -0,0 +1,8 @@
> +// { dg-do compile }
> +
> +template <typename T> class A {
> + template <void (A::*p)()> class C; // #1
> + template <void (A::*q)()> friend class C; // #2
> +};
> +
> +A<double> a;
>
prev parent reply other threads:[~2018-12-06 1:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 22:33 Alexandre Oliva
2018-12-06 1:17 ` 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=2ea1509b-af63-520a-05c1-be94f5305b28@redhat.com \
--to=jason@redhat.com \
--cc=aoliva@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nathan@acm.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).