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/105242] New: [OpenMP] ICE with EXIT in collapsed loop: in gfc_trans_exit, at fortran/trans-stmt.cc:6147 Date: Tue, 12 Apr 2022 16:43:14 +0000 [thread overview] Message-ID: <bug-105242-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105242 Bug ID: 105242 Summary: [OpenMP] ICE with EXIT in collapsed loop: in gfc_trans_exit, at fortran/trans-stmt.cc:6147 Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: ice-on-valid-code, openmp Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: jakub at gcc dot gnu.org Target Milestone: --- The following code (reduced code from a real-world project) gives an ICE but compiles with other vendors' compilers. It fails with GCC 10, 11 and trunk/12 with: 8 | if (kk == 7) exit | 1 internal compiler error: in gfc_trans_exit, at fortran/trans-stmt.cc:6147 0x69734b gfc_trans_exit(gfc_code*) ../../repos/gcc/gcc/fortran/trans-stmt.cc:6147 0xa17360 trans_code ../../repos/gcc/gcc/fortran/trans.cc:1947 0xa9e4b5 gfc_trans_if_1 ../../repos/gcc/gcc/fortran/trans-stmt.cc:1484 0xaa84cf gfc_trans_if(gfc_code*) ../../repos/gcc/gcc/fortran/trans-stmt.cc:1516 0xa17563 trans_code ../../repos/gcc/gcc/fortran/trans.cc:2004 0xa8ad58 gfc_trans_omp_code ../../repos/gcc/gcc/fortran/trans-openmp.cc:4399 0xa9a6aa gfc_trans_omp_do ../../repos/gcc/gcc/fortran/trans-openmp.cc:5381 !$omp target parallel do simd collapse(3) do ii = i1, i2 do jj = j1, j2 do kk = k1, k2 if (kk > 5) then k = 0 end if if (kk == 7) exit end do end do end do !$omp end target parallel do simd end
next reply other threads:[~2022-04-12 16:43 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-12 16:43 burnus at gcc dot gnu.org [this message] 2022-04-13 6:46 ` [Bug fortran/105242] " burnus at gcc dot gnu.org 2022-04-13 11:25 ` jakub at gcc dot gnu.org 2022-04-13 14:58 ` burnus at gcc dot gnu.org 2022-04-13 15:30 ` burnus at gcc dot gnu.org 2022-04-13 16:41 ` cvs-commit at gcc dot gnu.org 2022-04-13 16:41 ` 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-105242-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).