public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/102312] [9/10/11/12 Regression] ICE in gfc_get_dtype_rank_type, at fortran/trans-types.c:1558 since r9-5424-g92f3a180aaf6f3cd
Date: Tue, 14 Sep 2021 07:23:43 +0000 [thread overview]
Message-ID: <bug-102312-4-zQBWhPXnTS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102312-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102312
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marxin at gcc dot gnu.org,
| |pault at gcc dot gnu.org
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Last reconfirmed| |2021-09-14
Summary|[12 Regression] ICE in |[9/10/11/12 Regression] ICE
|gfc_get_dtype_rank_type, at |in gfc_get_dtype_rank_type,
|fortran/trans-types.c:1558 |at
| |fortran/trans-types.c:1558
| |since
| |r9-5424-g92f3a180aaf6f3cd
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r9-5424-g92f3a180aaf6f3cd.
next prev parent reply other threads:[~2021-09-14 7:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 17:27 [Bug fortran/102312] New: [12 Regression] ICE in gfc_get_dtype_rank_type, at fortran/trans-types.c:1558 gscfq@t-online.de
2021-09-14 6:55 ` [Bug fortran/102312] " rguenth at gcc dot gnu.org
2021-09-14 7:23 ` marxin at gcc dot gnu.org [this message]
2022-03-31 19:13 ` [Bug fortran/102312] [9/10/11 Regression] ICE in gfc_get_dtype_rank_type, at fortran/trans-types.c:1558 since r9-5424-g92f3a180aaf6f3cd anlauf at gcc dot gnu.org
2022-05-06 8:31 ` jakub at gcc dot gnu.org
2022-09-30 21:08 ` [Bug fortran/102312] [10/11 " anlauf at gcc dot gnu.org
2023-05-08 12:22 ` rguenth at gcc dot gnu.org
2023-05-08 19:25 ` anlauf 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-102312-4-zQBWhPXnTS@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).