From: Nathan Sidwell <nathan@acm.org>
To: GCC Patches <gcc-patches@gcc.gnu.org>, Jason Merrill <jason@redhat.com>
Subject: [PR c++/86610] lambda captures in templates
Date: Wed, 16 Jan 2019 21:48:00 -0000 [thread overview]
Message-ID: <cb1d2107-6bc0-6b39-a933-685f6580ac05@acm.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 751 bytes --]
This PR reports a bug where we select a non-const operator function and
then apply it to a const object. That's happening because the
expression 'c[0]' is not dependent, so we figure end up resolving it.
But the lambda capture logic doesn't capture 'c' at that point and we
have a non-const qualified 'c'. At instantiation time we do the capture
and the by-value lambda results in const-qualified captures.
Jason, the orginal test in process_outer_var_ref looked a little funky
-- why not just processing_template_decl? That would satisfy what the
comment says it checking. Anyway changing the test to check DECL's
type-dependency makes the right things happen, and a bootstrap passes.
Could you review please.
nathan
--
Nathan Sidwell
[-- Attachment #2: pr86610.diff --]
[-- Type: text/x-patch, Size: 1502 bytes --]
2019-01-16 Nathan Sidwell <nathan@acm.org>
PR c++/86610
* semantics.c (process_outer_var_ref): Only skip dependent types
in templates.
PR c++/86610
* g++.dg/cpp0x/pr86610.C: New.
Index: cp/semantics.c
===================================================================
--- cp/semantics.c (revision 267983)
+++ cp/semantics.c (working copy)
@@ -3438,10 +3438,9 @@ process_outer_var_ref (tree decl, tsubst
}
/* In a lambda within a template, wait until instantiation
- time to implicitly capture. */
+ time to implicitly capture a dependent type. */
if (context == containing_function
- && DECL_TEMPLATE_INFO (containing_function)
- && uses_template_parms (DECL_TI_ARGS (containing_function)))
+ && dependent_type_p (TREE_TYPE (decl)))
return decl;
if (lambda_expr && VAR_P (decl)
Index: testsuite/g++.dg/cpp0x/pr86610.C
===================================================================
--- testsuite/g++.dg/cpp0x/pr86610.C (revision 0)
+++ testsuite/g++.dg/cpp0x/pr86610.C (working copy)
@@ -0,0 +1,31 @@
+// { dg-do run { target c++11 } }
+// PR c++86610 lambda capture inside template
+
+struct C
+{
+ int operator[](int)
+ { return 1; }
+
+ int operator[](int) const
+ { return 0; } // Want this one
+};
+
+int q()
+{
+ C c;
+ return [=] { return c[0]; }();
+}
+
+template <typename T>
+int f()
+{
+ C c;
+ T d;
+ return [=] { return c[0]; }()
+ + [=] { return c[0] + d[0]; }();
+}
+
+int main()
+{
+ return q () + f<C>();
+}
next reply other threads:[~2019-01-16 21:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 21:48 Nathan Sidwell [this message]
2019-01-16 22:32 ` Jason Merrill
2019-01-22 22:25 ` H.J. Lu
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=cb1d2107-6bc0-6b39-a933-685f6580ac05@acm.org \
--to=nathan@acm.org \
--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).