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++/101717] [9/10 Regression] ICE capturing static member within stateless generic lambda
Date: Thu, 12 May 2022 21:15:20 +0000	[thread overview]
Message-ID: <bug-101717-4-DIKxrYihQW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101717-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101717

--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:

https://gcc.gnu.org/g:20dc7a2119cc0a4e5ddc4a6899a7350621f05440

commit r10-10721-g20dc7a2119cc0a4e5ddc4a6899a7350621f05440
Author: Jason Merrill <jason@redhat.com>
Date:   Wed Apr 6 22:20:49 2022 -0400

    c++: nested generic lambda in DMI [PR101717]

    We were already checking COMPLETE_TYPE_P to recognize instantiation of a
    generic lambda, but didn't consider that we might be nested in a
non-generic
    lambda.

            PR c++/101717

    gcc/cp/ChangeLog:

            * lambda.c (lambda_expr_this_capture): Check all enclosing
            lambdas for completeness.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp1y/lambda-generic-this4.C: New test.

  parent reply	other threads:[~2022-05-12 21:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02  0:21 [Bug c++/101717] New: ICE capturing static member by ref within stateless lambda johelegp at gmail dot com
2021-08-02  0:24 ` [Bug c++/101717] ICE capturing static member within stateless generic lambda johelegp at gmail dot com
2021-08-02 17:17 ` [Bug c++/101717] [12 Regression] " pinskia at gcc dot gnu.org
2021-08-02 17:17 ` pinskia at gcc dot gnu.org
2021-08-03 22:23 ` StevenSun2021 at hotmail dot com
2021-08-03 22:51 ` pinskia at gcc dot gnu.org
2021-08-03 23:28 ` StevenSun2021 at hotmail dot com
2021-12-29  0:03 ` [Bug c++/101717] [9/10/11/12 " pinskia at gcc dot gnu.org
2022-01-17 13:58 ` rguenth at gcc dot gnu.org
2022-01-31 15:59 ` marxin at gcc dot gnu.org
2022-04-07  2:00 ` jason at gcc dot gnu.org
2022-04-07  3:26 ` cvs-commit at gcc dot gnu.org
2022-04-12 20:14 ` [Bug c++/101717] [9/10/11 " cvs-commit at gcc dot gnu.org
2022-05-12 21:15 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-13 17:41 ` [Bug c++/101717] [9 " cvs-commit at gcc dot gnu.org
2022-05-13 17:47 ` 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-101717-4-DIKxrYihQW@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: 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).