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] [OpenMP] ICE with EXIT in collapsed loop: in gfc_trans_exit, at fortran/trans-stmt.cc:6147
Date: Wed, 13 Apr 2022 14:58:31 +0000 [thread overview]
Message-ID: <bug-105242-4-WR0wYkOxhA@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
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2022-04-13
Ever confirmed|0 |1
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |burnus at gcc dot gnu.org
--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #2)
> Why do you say accepts invalid for C/C++?
Because I messed up initially due to doing do much in parallel, found the
issue, but forget to delete that line before hitting 'save'.
I have patch – the problem is that the check does exist, but only takes care of
a small subset of directives.
next prev parent reply other threads:[~2022-04-13 14:58 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 [this message]
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-WR0wYkOxhA@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: link
Be 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).