public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/100607] ICE with SELECT RANK
Date: Mon, 06 Jun 2022 21:33:10 +0000 [thread overview]
Message-ID: <bug-100607-4-hc7w7QfRZf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100607-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100607
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #1 from kargl at gcc dot gnu.org ---
I have no idea what the problem is here. The code cleanly dies if the invalid
code is left in place. It compiles and runs if the invalid code is removed.
Perhaps, the bug was fixed in the last year. Tobias, plaease check.
next prev parent reply other threads:[~2022-06-06 21:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 21:10 [Bug fortran/100607] New: " burnus at gcc dot gnu.org
2021-05-16 13:34 ` [Bug fortran/100607] " dominiq at lps dot ens.fr
2022-06-06 21:33 ` kargl at gcc dot gnu.org [this message]
2022-06-07 4:35 ` kargl at gcc dot gnu.org
2023-04-03 1:27 ` kargl at gcc dot gnu.org
2023-04-03 20:16 ` anlauf at gcc dot gnu.org
2023-04-03 20:32 ` anlauf at gcc dot gnu.org
2023-04-03 21:28 ` sgk at troutmask dot apl.washington.edu
2023-05-29 23:10 ` kargl at gcc dot gnu.org
2023-06-01 19:26 ` anlauf at gcc dot gnu.org
2023-06-01 19:47 ` sgk at troutmask dot apl.washington.edu
2023-06-02 16:28 ` anlauf at gcc dot gnu.org
2023-06-02 17:59 ` cvs-commit at gcc dot gnu.org
2023-06-02 18:06 ` anlauf at gcc dot gnu.org
2023-06-02 18:17 ` sgk at troutmask dot apl.washington.edu
2023-06-03 18:21 ` cvs-commit at gcc dot gnu.org
2023-06-04 18:13 ` cvs-commit at gcc dot gnu.org
2023-06-04 18:22 ` cvs-commit 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-100607-4-hc7w7QfRZf@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).