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 fortran/105242] [OpenMP] ICE with EXIT in collapsed loop: in gfc_trans_exit, at fortran/trans-stmt.cc:6147 Date: Wed, 13 Apr 2022 16:41:10 +0000 [thread overview] Message-ID: <bug-105242-4-tg2hGFiPj1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105242-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105242 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tobias Burnus <burnus@gcc.gnu.org>: https://gcc.gnu.org/g:469fad0161afeb9369010ad498198297993ca592 commit r12-8145-g469fad0161afeb9369010ad498198297993ca592 Author: Tobias Burnus <tobias@codesourcery.com> Date: Wed Apr 13 18:40:52 2022 +0200 OpenMP/Fortran: Fix EXIT in loop diagnostic [PR105242] gcc/fortran/ChangeLog: PR fortran/105242 * match.cc (match_exit_cycle): Handle missing OMP LOOP, DO and SIMD directives in the EXIT/CYCLE diagnostic. gcc/testsuite/ChangeLog: PR fortran/105242 * gfortran.dg/gomp/loop-exit.f90: New test.
next prev parent reply other threads:[~2022-04-13 16:41 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-12 16:43 [Bug fortran/105242] New: " burnus at gcc dot gnu.org 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 [this message] 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-tg2hGFiPj1@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).