public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99833] [8/9/10/11 Regression] structured binding + if init + generic lambda = internal compiler error
Date: Wed, 14 Apr 2021 10:36:56 +0000	[thread overview]
Message-ID: <bug-99833-4-JzxWVZK8kU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99833-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
And that ICEs since r7-4511-g70f40fea6a317d7be82d1f02defb59381c7752e7 when
structured binding support has been added, first with
internal compiler error: in is_normal_capture_proxy, at cp/lambda.c:271
then is accepted since r8-6835-g6f58bc5825c0d0ff0606b747b01bb2dcff882a1d
and then since r8-7613-g1456e764105702a0bb6c9be13d8eef7f21990a79 ICEs in
tsubst_decomp_names.

  parent reply	other threads:[~2021-04-14 10:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-30 17:17 [Bug c++/99833] New: " nickgray0 at brown dot edu
2021-03-30 20:24 ` [Bug c++/99833] [8/9/10/11 Regression] " mpolacek at gcc dot gnu.org
2021-03-30 20:57 ` mpolacek at gcc dot gnu.org
2021-03-30 20:58 ` mpolacek at gcc dot gnu.org
2021-03-30 21:28 ` ppalka at gcc dot gnu.org
2021-03-31  7:56 ` rguenth at gcc dot gnu.org
2021-03-31 17:24 ` ppalka at gcc dot gnu.org
2021-04-14  9:40 ` jakub at gcc dot gnu.org
2021-04-14  9:54 ` jakub at gcc dot gnu.org
2021-04-14 10:36 ` jakub at gcc dot gnu.org [this message]
2021-04-14 11:14 ` jakub at gcc dot gnu.org
2021-04-14 12:25 ` ppalka at gcc dot gnu.org
2021-04-16  7:33 ` cvs-commit at gcc dot gnu.org
2021-04-16  7:35 ` [Bug c++/99833] [8/9/10 " jakub at gcc dot gnu.org
2021-04-20  9:46 ` cvs-commit at gcc dot gnu.org
2021-04-20  9:53 ` [Bug c++/99833] [8/9 " jakub at gcc dot gnu.org
2021-04-20 23:34 ` cvs-commit at gcc dot gnu.org
2021-04-22 16:53 ` cvs-commit at gcc dot gnu.org
2021-04-22 17:11 ` jakub 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-99833-4-JzxWVZK8kU@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).