From: Patrick Palka <patrick@parcs.ath.cx>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Jason Merrill <jason@redhat.com>, Patrick Palka <patrick@parcs.ath.cx>
Subject: Re: [PATCH] Fix PR c++/66786 (ICE with nested lambdas in variable template)
Date: Wed, 02 Mar 2016 17:52:00 -0000 [thread overview]
Message-ID: <CA+C-WL86nrCVm9bj5k1a2=Wm0oikzM5sDKWoKi7cDziYGVAAdg@mail.gmail.com> (raw)
In-Reply-To: <CA+C-WL83C4bOAsizD8P8v4P=kRwWvPK8j+AfBXMfEL3Em=fc+A@mail.gmail.com>
On Mon, Feb 15, 2016 at 9:42 AM, Patrick Palka <patrick@parcs.ath.cx> wrote:
> On Mon, Feb 8, 2016 at 12:19 AM, Patrick Palka <patrick@parcs.ath.cx> wrote:
>> Here, we are calling template_class_depth on a FIELD_DECL corresponding
>> to a lambda that is used inside variable template. template_class_depth
>> however does not see that this FIELD_DECL is used inside a variable
>> template binding because its chain of DECL_CONTEXTs does not include the
>> corresponding VAR_DECL. So template_class_depth returns the wrong
>> template nesting level which causes its callers to malfunction. In
>> particular we strip a template argument level in
>> tsubst_copy [FIELD_DECL] when we shouldn't have.
>>
>> This patch makes template_class_depth look at a lambda type's
>> LAMBDA_TYPE_EXTRA_SCOPE field instead of its TYPE_CONTEXT, so that it
>> can iterate into an enclosing variable template, if applicable.
>>
>> Tested on x86_64-pc-linux gnu, no new regressions. Also tested against
>> Boost. Is this OK to commit?
>>
>> gcc/cp/ChangeLog:
>>
>> PR c++/66786
>> * pt.c (template_class_depth): Given a lambda type, iterate
>> into its LAMBDA_TYPE_EXTRA_SCOPE field instead of its
>> TYPE_CONTEXT. Given a VAR_DECL, iterate into its
>> CP_DECL_CONTEXT.
>>
>> gcc/testsuite/ChangeLog:
>>
>> PR c++/66786
>> * g++.dg/cpp1y/var-templ48.C: New test.
>> * g++.dg/cpp1y/var-templ49.C: New test.
>> ---
>> gcc/cp/pt.c | 12 ++++++++----
>> gcc/testsuite/g++.dg/cpp1y/var-templ48.C | 5 +++++
>> gcc/testsuite/g++.dg/cpp1y/var-templ49.C | 9 +++++++++
>> 3 files changed, 22 insertions(+), 4 deletions(-)
>> create mode 100644 gcc/testsuite/g++.dg/cpp1y/var-templ48.C
>> create mode 100644 gcc/testsuite/g++.dg/cpp1y/var-templ49.C
>>
>> diff --git a/gcc/cp/pt.c b/gcc/cp/pt.c
>> index 4d405cf..5c344c1 100644
>> --- a/gcc/cp/pt.c
>> +++ b/gcc/cp/pt.c
>> @@ -369,16 +369,20 @@ template_class_depth (tree type)
>> {
>> int depth;
>>
>> - for (depth = 0;
>> - type && TREE_CODE (type) != NAMESPACE_DECL;
>> - type = (TREE_CODE (type) == FUNCTION_DECL)
>> - ? CP_DECL_CONTEXT (type) : CP_TYPE_CONTEXT (type))
>> + for (depth = 0; type && TREE_CODE (type) != NAMESPACE_DECL; )
>> {
>> tree tinfo = get_template_info (type);
>>
>> if (tinfo && PRIMARY_TEMPLATE_P (TI_TEMPLATE (tinfo))
>> && uses_template_parms (INNERMOST_TEMPLATE_ARGS (TI_ARGS (tinfo))))
>> ++depth;
>> +
>> + if (VAR_OR_FUNCTION_DECL_P (type))
>> + type = CP_DECL_CONTEXT (type);
>> + else if (LAMBDA_TYPE_P (type))
>> + type = LAMBDA_TYPE_EXTRA_SCOPE (type);
>> + else
>> + type = CP_TYPE_CONTEXT (type);
>> }
>>
>> return depth;
>> diff --git a/gcc/testsuite/g++.dg/cpp1y/var-templ48.C b/gcc/testsuite/g++.dg/cpp1y/var-templ48.C
>> new file mode 100644
>> index 0000000..f0c7693
>> --- /dev/null
>> +++ b/gcc/testsuite/g++.dg/cpp1y/var-templ48.C
>> @@ -0,0 +1,5 @@
>> +// PR c++/66786
>> +// { dg-do compile { target c++14 } }
>> +
>> +template <typename... T> auto list = [](T... xs) { [=](auto f) { f(xs...); }; };
>> +int main() { list<int>(0); }
>> diff --git a/gcc/testsuite/g++.dg/cpp1y/var-templ49.C b/gcc/testsuite/g++.dg/cpp1y/var-templ49.C
>> new file mode 100644
>> index 0000000..cd3f230
>> --- /dev/null
>> +++ b/gcc/testsuite/g++.dg/cpp1y/var-templ49.C
>> @@ -0,0 +1,9 @@
>> +// PR c++/66786
>> +// { dg-do compile { target c++14 } }
>> +
>> +int f (int, bool);
>> +
>> +template <typename>
>> +auto list = [](auto... xs) { return [=](auto f, auto... ys) { return f(xs..., ys...); }; };
>> +
>> +const int &a = list<int>(0, true)(f);
>> --
>> 2.7.1.257.g925a48d
>>
>
> Ping.
Ping
next prev parent reply other threads:[~2016-03-02 17:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 5:19 Patrick Palka
2016-02-15 14:43 ` Patrick Palka
2016-03-02 17:52 ` Patrick Palka [this message]
2016-03-04 23:38 ` Jason Merrill
2016-03-06 6:42 ` Jason Merrill
2016-03-06 14:30 ` Patrick Palka
2016-03-07 14:08 ` Jason Merrill
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='CA+C-WL86nrCVm9bj5k1a2=Wm0oikzM5sDKWoKi7cDziYGVAAdg@mail.gmail.com' \
--to=patrick@parcs.ath.cx \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@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).