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++/106567] [13 Regression] An array with a dependent type and initializer-deduced bound is treated as an array of unknown bound when captured in a lambda Date: Mon, 12 Sep 2022 17:50:52 +0000 [thread overview] Message-ID: <bug-106567-4-3ivFrW3FRT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106567-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106567 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:7c989a8ed47228bdd494a2f0d1f6fdd325f953d7 commit r13-2628-g7c989a8ed47228bdd494a2f0d1f6fdd325f953d7 Author: Jason Merrill <jason@redhat.com> Date: Mon Sep 12 12:59:46 2022 -0400 c++: lambda capture of array with deduced bounds [PR106567] We can't use the type of an array variable directly if we haven't deduced its length yet. 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.
next prev parent reply other threads:[~2022-09-12 17:50 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-08 20:36 [Bug c++/106567] New: " ville.voutilainen at gmail dot com 2022-08-08 20:49 ` [Bug c++/106567] [13 regression] " ville.voutilainen at gmail dot com 2022-08-08 21:02 ` pinskia at gcc dot gnu.org 2022-08-08 21:03 ` pinskia at gcc dot gnu.org 2022-08-08 21:07 ` mpolacek at gcc dot gnu.org 2022-08-08 21:08 ` [Bug c++/106567] [13 Regression] " mpolacek at gcc dot gnu.org 2022-08-09 8:13 ` m.cencora at gmail dot com 2022-09-12 16:55 ` jason at gcc dot gnu.org 2022-09-12 17:50 ` cvs-commit at gcc dot gnu.org [this message] 2022-09-13 20:29 ` ville.voutilainen at gmail dot com 2022-09-15 10:14 ` jason 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-106567-4-3ivFrW3FRT@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: linkBe 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).