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 fortran/109622] [13/14 regression][OpenACC] internal compiler error: in omp_group_base, at gimplify.cc:9412 if -fopenacc is set. Date: Tue, 25 Apr 2023 13:59:21 +0000 [thread overview] Message-ID: <bug-109622-4-Rpt8T9uu8K@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109622-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109622 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jules at gcc dot gnu.org Summary|[13/14 regression] internal |[13/14 regression][OpenACC] |compiler error: in |internal compiler error: in |omp_group_base, at |omp_group_base, at |gimplify.cc:9412 if |gimplify.cc:9412 if |-fopenacc is set. |-fopenacc is set. --- Comment #6 from Tobias Burnus <burnus at gcc dot gnu.org> --- The ICE is in omp_group_base, which was added by Julian in r13-2661-gb57abd072dd319a72839a49e769bffc244a52bc0 and updated in later commits. The debugger shows: Breakpoint 1, omp_index_mapping_groups_1 (grpmap=0x2d2f960, groups=0x2cc4700, reindex_sentinel=0x0) at ../../repos/gcc/gcc/gimplify.cc:9426 9426 { (gdb) n 9431 FOR_EACH_VEC_ELT (*groups, i, grp) ... 9441 tree node = omp_group_base (grp, &chained, &fpp); for the last grp (i = 1, there are only 2). 9292 omp_group_base (omp_mapping_group *grp, unsigned int *chained, 9293 tree *firstprivate) 9294 { 9295 tree node = *grp->grp_start; (gdb) p debug(*grp->grp_start) map(attach_detach:atransform2->next [bias: 0]) Which fails at 'gcc_unreachable' for 'switch (OMP_CLAUSE_MAP_KIND (node))'. * * * I note that case GOMP_MAP_ATTACH: case GOMP_MAP_DETACH: are handled but GOMP_MAP_ATTACH_DETACH isn't. Actually, it is handled but not as separate input but as: case ....: ... node = OMP_CLAUSE_CHAIN (node); switch (OMP_CLAUSE_MAP_KIND (node)) ... case GOMP_MAP_ATTACH_DETACH: * * * The original input is ("debug(...)" for i = 0, which shows i=0 and i=1): map(attach:*atransform2->next [bias: 184]) map(attach_detach:atransform2->next [bias: 0]) which is fine, but as FOR_EACH_VEC_ELT (*groups, i, grp) then also processes i=1 separately, it fails.
next prev parent reply other threads:[~2023-04-25 13:59 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-25 10:27 [Bug fortran/109622] New: " patrick.begou@univ-grenoble-alpes.fr 2023-04-25 10:29 ` [Bug fortran/109622] " patrick.begou@univ-grenoble-alpes.fr 2023-04-25 10:32 ` patrick.begou@univ-grenoble-alpes.fr 2023-04-25 12:25 ` patrick.begou@univ-grenoble-alpes.fr 2023-04-25 12:49 ` pault at gcc dot gnu.org 2023-04-25 12:51 ` [Bug fortran/109622] [13/14 regression] " pault at gcc dot gnu.org 2023-04-25 13:20 ` rguenth at gcc dot gnu.org 2023-04-25 13:59 ` burnus at gcc dot gnu.org [this message] 2023-04-25 16:38 ` [Bug fortran/109622] [13/14 regression][OpenACC] " patrick.begou@univ-grenoble-alpes.fr 2023-04-26 6:58 ` rguenth at gcc dot gnu.org 2023-04-28 11:03 ` burnus at gcc dot gnu.org 2023-04-28 11:34 ` cvs-commit at gcc dot gnu.org 2023-04-29 9:41 ` patrick.begou@univ-grenoble-alpes.fr 2023-05-04 11:52 ` cvs-commit at gcc dot gnu.org 2023-05-05 13:15 ` cvs-commit at gcc dot gnu.org 2023-05-05 13:15 ` cvs-commit at gcc dot gnu.org 2023-05-08 12:35 ` tschwinge at gcc dot gnu.org 2023-05-08 13:52 ` patrick.begou@univ-grenoble-alpes.fr 2023-05-08 13:56 ` burnus 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-109622-4-Rpt8T9uu8K@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).