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/104127] [9 Regression] ICE in get_array_charlen, at fortran/trans-array.c:7244 Date: Sat, 29 Jan 2022 23:17:18 +0000 [thread overview] Message-ID: <bug-104127-4-bkGUrPPfRM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104127-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104127 anlauf at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED --- Comment #11 from anlauf at gcc dot gnu.org --- Fixed on 9-branch for the reported testcase. The extended testcase committed on 10-branch and higher needed deactivating of two lines which seem to require additional fixes and likely failed before. Closing. Thanks for the report!
prev parent reply other threads:[~2022-01-29 23:17 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-19 18:46 [Bug fortran/104127] New: [9/10/11/12 " gscfq@t-online.de 2022-01-19 19:24 ` [Bug fortran/104127] " anlauf at gcc dot gnu.org 2022-01-19 19:49 ` anlauf at gcc dot gnu.org 2022-01-19 20:43 ` anlauf at gcc dot gnu.org 2022-01-20 7:56 ` rguenth at gcc dot gnu.org 2022-01-20 10:16 ` marxin at gcc dot gnu.org 2022-01-20 21:49 ` anlauf at gcc dot gnu.org 2022-01-22 15:09 ` cvs-commit at gcc dot gnu.org 2022-01-26 18:16 ` cvs-commit at gcc dot gnu.org 2022-01-29 22:06 ` cvs-commit at gcc dot gnu.org 2022-01-29 22:33 ` [Bug fortran/104127] [9 " anlauf at gcc dot gnu.org 2022-01-29 23:14 ` cvs-commit at gcc dot gnu.org 2022-01-29 23:17 ` anlauf at gcc dot gnu.org [this message]
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-104127-4-bkGUrPPfRM@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).