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/103692] [11/12 Regression] ICE in add_init_expr_to_sym, at fortran/decl.c:2062 Date: Thu, 20 Jan 2022 21:59:27 +0000 [thread overview] Message-ID: <bug-103692-4-xW4X3i9Wlt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103692-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103692 --- 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:0351d851f791d81d85d4c366755e0662ea67dc97 commit r11-9483-g0351d851f791d81d85d4c366755e0662ea67dc97 Author: Harald Anlauf <anlauf@gmx.de> Date: Mon Jan 17 22:52:08 2022 +0100 Fortran: handle expansion of zero-sized array constructors gcc/fortran/ChangeLog: PR fortran/103692 * array.c (gfc_expand_constructor): Handle zero-sized array constructors. gcc/testsuite/ChangeLog: PR fortran/103692 * gfortran.dg/pr102520.f90: Adjust error messages. * gfortran.dg/pr103692.f90: New test. (cherry picked from commit 0d01a2722671bef37b931fd1f121e44b27e68268)
next prev parent reply other threads:[~2022-01-20 21:59 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-13 19:52 [Bug fortran/103692] New: " gscfq@t-online.de 2021-12-13 20:38 ` [Bug fortran/103692] " anlauf at gcc dot gnu.org 2021-12-13 21:23 ` anlauf at gcc dot gnu.org 2021-12-14 10:07 ` marxin at gcc dot gnu.org 2022-01-04 11:08 ` rguenth at gcc dot gnu.org 2022-01-17 21:02 ` anlauf at gcc dot gnu.org 2022-01-17 21:59 ` anlauf at gcc dot gnu.org 2022-01-18 19:02 ` cvs-commit at gcc dot gnu.org 2022-01-20 21:59 ` cvs-commit at gcc dot gnu.org [this message] 2022-01-20 22:47 ` cvs-commit at gcc dot gnu.org 2022-01-20 22:48 ` 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-103692-4-xW4X3i9Wlt@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).