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/106209] ICE in add_init_expr_to_sym, at fortran/decl.cc:2132 Date: Sat, 04 Feb 2023 15:43:33 +0000 [thread overview] Message-ID: <bug-106209-4-30pyGlVO6z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106209-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106209 --- Comment #7 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:8e58d94ac56127ebca3a893284455032a707d948 commit r11-10505-g8e58d94ac56127ebca3a893284455032a707d948 Author: Harald Anlauf <anlauf@gmx.de> Date: Thu Jul 14 22:24:55 2022 +0200 Fortran: error recovery for bad initializers of implied-shape arrays [PR106209] gcc/fortran/ChangeLog: PR fortran/106209 * decl.c (add_init_expr_to_sym): Handle bad initializers for implied-shape arrays. gcc/testsuite/ChangeLog: PR fortran/106209 * gfortran.dg/pr106209.f90: New test. Co-authored-by: Steven G. Kargl <kargl@gcc.gnu.org> (cherry picked from commit 748f8a8b145dde59c7b63aa68b5a59515b7efc49)
next prev parent reply other threads:[~2023-02-04 15:43 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-05 18:49 [Bug fortran/106209] New: " gscfq@t-online.de 2022-07-05 19:21 ` [Bug fortran/106209] " kargl at gcc dot gnu.org 2022-07-14 19:35 ` anlauf at gcc dot gnu.org 2022-07-14 20:17 ` sgk at troutmask dot apl.washington.edu 2022-07-14 20:27 ` cvs-commit at gcc dot gnu.org 2022-07-14 20:36 ` anlauf at gcc dot gnu.org 2023-01-28 22:03 ` cvs-commit at gcc dot gnu.org 2023-02-04 15:43 ` cvs-commit at gcc dot gnu.org [this message] 2023-02-05 18:55 ` 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-106209-4-30pyGlVO6z@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).