public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/102312] [10/11 Regression] ICE in gfc_get_dtype_rank_type, at fortran/trans-types.c:1558 since r9-5424-g92f3a180aaf6f3cd Date: Fri, 30 Sep 2022 21:08:06 +0000 [thread overview] Message-ID: <bug-102312-4-W8RjOXccS6@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 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |WAITING CC| |anlauf at gcc dot gnu.org --- Comment #5 from anlauf at gcc dot gnu.org --- Both testcases work for me on current mainline. Do we know what fixed it?
next prev parent reply other threads:[~2022-09-30 21:08 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 ` [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 marxin at gcc dot gnu.org 2022-03-31 19:13 ` [Bug fortran/102312] [9/10/11 " anlauf at gcc dot gnu.org 2022-05-06 8:31 ` jakub at gcc dot gnu.org 2022-09-30 21:08 ` anlauf at gcc dot gnu.org [this message] 2023-05-08 12:22 ` [Bug fortran/102312] [10/11 " 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-W8RjOXccS6@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).