public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/100291] [8/9/10/11/12 Regression] internal compiler error: trying to capture ‘this’ in instantiation of generic lambda
Date: Tue, 27 Apr 2021 17:12:22 +0000 [thread overview]
Message-ID: <bug-100291-4-UMhl1GkLTu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100291-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100291
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
Target Milestone|--- |8.5
Keywords| |ice-on-invalid-code
Summary|internal compiler error: |[8/9/10/11/12 Regression]
|trying to capture ‘this’ in |internal compiler error:
|instantiation of generic |trying to capture ‘this’ in
|lambda |instantiation of generic
| |lambda
CC| |nathan at gcc dot gnu.org
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
I think this is ICE-on-invalid. Started with r245065:
/home/mpolacek/w.C:119:57: internal compiler error: in
finish_member_declaration, at cp/semantics.c:2969
[&](auto, auto cmp) { SingleStepper::time(cmp.state); });
~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~
0x9ac65b finish_member_declaration(tree_node*)
../../gcc/cp/semantics.c:2966
0xa52ce3 add_capture(tree_node*, tree_node*, tree_node*, bool, bool)
../../gcc/cp/lambda.c:600
0xa53090 add_default_capture(tree_node*, tree_node*, tree_node*)
../../gcc/cp/lambda.c:669
0xa538dd lambda_expr_this_capture(tree_node*, bool)
../../gcc/cp/lambda.c:760
0xa53ca1 maybe_resolve_dummy(tree_node*, bool)
../../gcc/cp/lambda.c:827
0x787891 build_new_method_call_1
../../gcc/cp/call.c:8760
0x787f30 build_new_method_call(tree_node*, tree_node*, vec<tree_node*, va_gc,
vl_embed>**, tree_node*, int, tree_node**, int)
../../gcc/cp/call.c:8870
0x83ef22 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
../../gcc/cp/pt.c:17279
0x83a881 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
../../gcc/cp/pt.c:16401
0x834e7e tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
../../gcc/cp/pt.c:15669
0x8369b0 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
../../gcc/cp/pt.c:15879
0x8369b0 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
../../gcc/cp/pt.c:15879
0x858968 instantiate_decl(tree_node*, int, bool)
../../gcc/cp/pt.c:22817
0x8c2790 maybe_instantiate_decl
../../gcc/cp/decl2.c:5008
0x8c3060 mark_used(tree_node*, int)
../../gcc/cp/decl2.c:5107
0x784968 build_over_call
../../gcc/cp/call.c:8088
0x77593c build_op_call_1
../../gcc/cp/call.c:4518
0x775acc build_op_call(tree_node*, vec<tree_node*, va_gc, vl_embed>**, int)
../../gcc/cp/call.c:4544
0x9aa173 finish_call_expr(tree_node*, vec<tree_node*, va_gc, vl_embed>**, bool,
bool, int)
../../gcc/cp/semantics.c:2458
0x83ef56 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
../../gcc/cp/pt.c:17286
next prev parent reply other threads:[~2021-04-27 17:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 17:06 [Bug c++/100291] New: " mpolacek at gcc dot gnu.org
2021-04-27 17:12 ` mpolacek at gcc dot gnu.org [this message]
2021-05-14 9:54 ` [Bug c++/100291] [9/10/11/12 Regression] " jakub at gcc dot gnu.org
2021-06-01 8:20 ` rguenth at gcc dot gnu.org
2022-05-27 9:45 ` [Bug c++/100291] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:44 ` jakub at gcc dot gnu.org
2023-07-07 10:39 ` [Bug c++/100291] [11/12/13/14 " rguenth at gcc dot gnu.org
2023-10-25 20:21 ` ppalka at gcc dot gnu.org
2023-10-25 20:27 ` ppalka 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-100291-4-UMhl1GkLTu@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).