public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/104211] ICE in find_array_section, at fortran/expr.cc:1720 Date: Wed, 16 Feb 2022 21:35:45 +0000 [thread overview] Message-ID: <bug-104211-4-oZtdDhHk3V@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104211-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104211 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>: https://gcc.gnu.org/g:3982a308e669cc5537322c83e8c2d49b0144297e commit r11-9579-g3982a308e669cc5537322c83e8c2d49b0144297e Author: Harald Anlauf <anlauf@gmx.de> Date: Thu Feb 10 21:22:48 2022 +0100 Fortran: improve error recovery on bad array section gcc/fortran/ChangeLog: PR fortran/104211 * expr.c (find_array_section): Replace assertion by error recovery when encountering bad array constructor. gcc/testsuite/ChangeLog: PR fortran/104211 * gfortran.dg/pr104211.f90: New test. (cherry picked from commit 19b517dff37b8e25f6babf8883483be73cad8fb3)
next prev parent reply other threads:[~2022-02-16 21:35 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-24 19:00 [Bug fortran/104211] New: " gscfq@t-online.de 2022-01-24 20:01 ` [Bug fortran/104211] " anlauf at gcc dot gnu.org 2022-02-10 20:29 ` anlauf at gcc dot gnu.org 2022-02-14 20:07 ` cvs-commit at gcc dot gnu.org 2022-02-16 21:35 ` cvs-commit at gcc dot gnu.org [this message] 2022-02-16 21:37 ` 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-104211-4-oZtdDhHk3V@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).