public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: gcc-patches@gcc.gnu.org
Cc: Ville Voutilainen <ville.voutilainen@gmail.com>
Subject: [PATCH] c++: lambda capture of array with deduced bounds [PR106567]
Date: Mon, 12 Sep 2022 13:50:41 -0400	[thread overview]
Message-ID: <20220912175041.3406947-1-jason@redhat.com> (raw)

We can't use the type of an array variable directly if we haven't deduced
its length yet.

Tested x86_64-pc-linux-gnu, applying to trunk.

	PR c++/106567

gcc/cp/ChangeLog:

	* lambda.cc (type_deducible_expression_p): Check
	array_of_unknown_bound_p.

gcc/testsuite/ChangeLog:

	* g++.dg/cpp0x/lambda/lambda-array4.C: New test.
---
 gcc/cp/lambda.cc                              |  1 +
 .../g++.dg/cpp0x/lambda/lambda-array4.C       | 29 +++++++++++++++++++
 2 files changed, 30 insertions(+)
 create mode 100644 gcc/testsuite/g++.dg/cpp0x/lambda/lambda-array4.C

diff --git a/gcc/cp/lambda.cc b/gcc/cp/lambda.cc
index 3fb98a98057..3ee1fe9489e 100644
--- a/gcc/cp/lambda.cc
+++ b/gcc/cp/lambda.cc
@@ -198,6 +198,7 @@ type_deducible_expression_p (tree expr)
   tree t = non_reference (TREE_TYPE (expr));
   return (t && TREE_CODE (t) != TYPE_PACK_EXPANSION
 	  && !WILDCARD_TYPE_P (t) && !LAMBDA_TYPE_P (t)
+	  && !array_of_unknown_bound_p (t)
 	  && !type_uses_auto (t));
 }
 
diff --git a/gcc/testsuite/g++.dg/cpp0x/lambda/lambda-array4.C b/gcc/testsuite/g++.dg/cpp0x/lambda/lambda-array4.C
new file mode 100644
index 00000000000..94ec7f8457e
--- /dev/null
+++ b/gcc/testsuite/g++.dg/cpp0x/lambda/lambda-array4.C
@@ -0,0 +1,29 @@
+// PR c++/106567
+// { dg-do compile { target c++11 } }
+
+template <class V>
+void urgh()
+{
+    const V x[] = {V(0), V(1), V(2), V(0)};
+
+    [&]() {
+        for (auto& v : x) {}
+    }();
+}
+
+void no_urgh()
+{
+    using V = int;
+
+    const V x[] = {V(0), V(1), V(2), V(0)};
+
+    [&]() {
+        for (auto& v : x) {}
+    }();
+}
+
+int main()
+{
+    no_urgh();
+    urgh<int>();
+}

base-commit: 8ef5fa4c56c82dfbd6e8fc5e4e08c4be843abc3e
-- 
2.31.1


                 reply	other threads:[~2022-09-12 17:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220912175041.3406947-1-jason@redhat.com \
    --to=jason@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ville.voutilainen@gmail.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).