public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/108422] [13 Regression] ICE: base pointer cycle detected since r13-2661-gb57abd072dd319a7 Date: Mon, 20 Feb 2023 09:45:22 +0000 [thread overview] Message-ID: <bug-108422-4-3mP6ouINEr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108422-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108422 --- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> --- FOR_EACH_VEC_ELT (*groups, i, grp) { if (grp->mark != PERMANENT) if (!omp_tsort_mapping_groups_1 (&cursor, groups, grpmap, grp)) return NULL; } first processes: map(to:*(const struct ._anon_0 *) __closure) map(firstprivate:__closure [pointer assign, bias: 0]) map(tofrom:*__closure->__a [len: 4]) map(always_pointer:__closure->__a [pointer assign, bias: 0]) map(to:*__closure) map(to:*(const struct ._anon_0 *) __closure) which then has: *innerp == grp in omp_tsort_mapping_groups_1. The next VEC has: (gdb) p debug(*grp.grp_start) map(tofrom:*__closure->__a [len: 4]) map(always_pointer:__closure->__a [pointer assign, bias: 0]) map(to:*__closure) map(to:*(const struct ._anon_0 *) __closure) But the inner one is again the previous one: (gdb) p debug(**innerp.grp_start) map(to:*(const struct ._anon_0 *) __closure) map(firstprivate:__closure [pointer assign, bias: 0]) map(tofrom:*__closure->__a [len: 4]) map(always_pointer:__closure->__a [pointer assign, bias: 0]) map(to:*__closure) map(to:*(const struct ._anon_0 *) __closure) where: (gdb) p (*innerp)->mark $78 = PERMANENT Untested patch: --- a/gcc/gimplify.cc +++ b/gcc/gimplify.cc @@ -9643 +9643 @@ omp_tsort_mapping_groups_1 (omp_mapping_group ***outlist, - if (innerp && *innerp != grp) + if (innerp && *innerp != grp && (*innerp)->mark != PERMANENT)
next prev parent reply other threads:[~2023-02-20 9:45 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-16 17:49 [Bug c++/108422] New: [13 Regression] ICE: base pointer cycle detected gscfq@t-online.de 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 [this message] 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-3mP6ouINEr@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).