public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/108422] New: [13 Regression] ICE: base pointer cycle detected Date: Mon, 16 Jan 2023 17:49:48 +0000 [thread overview] Message-ID: <bug-108422-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108422 Bug ID: 108422 Summary: [13 Regression] ICE: base pointer cycle detected Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Started between 20220911 and 20220918 : $ cat z1.cc void foo (int a) { auto bar = [&]() { #pragma omp target parallel #pragma omp target ++a; }; bar(); } $ cat z2.cc void foo (int a) { auto bar = [&]() { #pragma omp target #pragma omp target ++a; }; bar(); } $ g++-13-20230115 -c z1.cc -fopenmp when processing group: map(to:*__closure) z1.cc: In lambda function: z1.cc:5:13: internal compiler error: base pointer cycle detected 5 | #pragma omp target parallel | ^~~ 0xc0a6f3 omp_tsort_mapping_groups_1 ../../gcc/gimplify.cc:9603 0xc0a515 omp_tsort_mapping_groups_1 ../../gcc/gimplify.cc:9646 0xc0a515 omp_tsort_mapping_groups_1 ../../gcc/gimplify.cc:9646 0xc1ee00 omp_tsort_mapping_groups ../../gcc/gimplify.cc:9684 0xc1ee00 gimplify_scan_omp_clauses ../../gcc/gimplify.cc:10771 0xc24fce gimplify_omp_workshare ../../gcc/gimplify.cc:15390 0xc10cca gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*), int) ../../gcc/gimplify.cc:16903 0xc14308 gimplify_stmt(tree_node**, gimple**) ../../gcc/gimplify.cc:7219 0xc14861 gimplify_bind_expr ../../gcc/gimplify.cc:1430 0xc10eea gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*), int) ../../gcc/gimplify.cc:16562 0xc14308 gimplify_stmt(tree_node**, gimple**) ../../gcc/gimplify.cc:7219 0xc11ccb gimplify_statement_list ../../gcc/gimplify.cc:2019 0xc11ccb gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*), int) ../../gcc/gimplify.cc:16806 0xc14308 gimplify_stmt(tree_node**, gimple**) ../../gcc/gimplify.cc:7219 0xc14861 gimplify_bind_expr ../../gcc/gimplify.cc:1430 0xc10eea gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*), int) ../../gcc/gimplify.cc:16562 0xc14308 gimplify_stmt(tree_node**, gimple**) ../../gcc/gimplify.cc:7219 0xc153ab gimplify_body(tree_node*, bool) ../../gcc/gimplify.cc:17623 0xc157fd gimplify_function_tree(tree_node*) ../../gcc/gimplify.cc:17822 0xa988e7 cgraph_node::analyze() ../../gcc/cgraphunit.cc:676
next reply other threads:[~2023-01-16 17:49 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-16 17:49 gscfq@t-online.de [this message] 2023-01-17 7:04 ` [Bug c++/108422] " rguenth at gcc dot gnu.org 2023-01-17 13:29 ` [Bug c++/108422] [13 Regression] ICE: base pointer cycle detected since r13-2661-gb57abd072dd319a7 marxin at gcc dot gnu.org 2023-02-20 9:26 ` burnus at gcc dot gnu.org 2023-02-20 9:45 ` burnus at gcc dot gnu.org 2023-02-20 10:02 ` burnus at gcc dot gnu.org 2023-02-21 13:05 ` rguenth at gcc dot gnu.org 2023-02-21 17:43 ` burnus at gcc dot gnu.org 2023-04-26 6:57 ` [Bug c++/108422] [13/14 " rguenth at gcc dot gnu.org 2023-07-27 9:25 ` rguenth at gcc dot gnu.org 2024-05-21 9:13 ` [Bug c++/108422] [13/14/15 " 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-108422-4@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).