public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/98205] ICE in expand_omp_for_generic, at omp-expand.c:4307 Date: Wed, 06 Jan 2021 09:39:44 +0000 [thread overview] Message-ID: <bug-98205-4-3ev0u4qGCm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98205-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98205 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:c925d4cebf817905c237aa2d93887f254b4a74f4 commit r10-9219-gc925d4cebf817905c237aa2d93887f254b4a74f4 Author: Jakub Jelinek <jakub@redhat.com> Date: Thu Dec 10 11:07:07 2020 +0100 openmp: Fix ICE with broken doacross loop [PR98205] If the loop body doesn't ever continue, we don't have a bb to insert the updates. Fixed by not adding them at all in that case. 2020-12-10 Jakub Jelinek <jakub@redhat.com> PR middle-end/98205 * omp-expand.c (expand_omp_for_generic): Fix up broken_loop handling. * c-c++-common/gomp/doacross-4.c: New test. (cherry picked from commit a2a17ae7d85e420db5fe0c7ab2f59a470e2c7a78)
next prev parent reply other threads:[~2021-01-06 9:39 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-08 17:40 [Bug c/98205] New: " gscfq@t-online.de 2020-12-09 12:02 ` [Bug middle-end/98205] " jakub at gcc dot gnu.org 2020-12-10 10:08 ` cvs-commit at gcc dot gnu.org 2021-01-06 9:39 ` cvs-commit at gcc dot gnu.org [this message] 2021-04-20 23:30 ` cvs-commit at gcc dot gnu.org 2021-04-22 16:49 ` cvs-commit at gcc dot gnu.org 2021-04-22 17:08 ` jakub at gcc dot gnu.org 2021-09-11 14:22 ` pinskia 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-98205-4-3ev0u4qGCm@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).