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/105633] ICE in find_array_section, at fortran/expr.cc:1582 Date: Sun, 23 Oct 2022 19:59:17 +0000 [thread overview] Message-ID: <bug-105633-4-iJFwFTI5LD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105633-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105633 --- 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:c6ff6ca2fcefdd5edc37011a2ba8412a466d9b0b commit r11-10330-gc6ff6ca2fcefdd5edc37011a2ba8412a466d9b0b Author: Harald Anlauf <anlauf@gmx.de> Date: Wed Oct 19 22:37:56 2022 +0200 Fortran: error recovery with references of bad array constructors [PR105633] gcc/fortran/ChangeLog: PR fortran/105633 * expr.c (find_array_section): Move check for NULL pointers so that both subscript triplets and vector subscripts are covered. gcc/testsuite/ChangeLog: PR fortran/105633 * gfortran.dg/pr105633.f90: New test. Co-authored-by: Steven G. Kargl <kargl@gcc.gnu.org> (cherry picked from commit ecb20df4fa6d99daa635c7fb662dc0554610777e)
next prev parent reply other threads:[~2022-10-23 19:59 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-17 18:44 [Bug fortran/105633] New: " gscfq@t-online.de 2022-05-17 19:12 ` [Bug fortran/105633] " kargl at gcc dot gnu.org 2022-10-19 20:16 ` anlauf at gcc dot gnu.org 2022-10-19 20:50 ` anlauf at gcc dot gnu.org 2022-10-20 20:20 ` cvs-commit at gcc dot gnu.org 2022-10-20 20:23 ` anlauf at gcc dot gnu.org 2022-10-23 19:56 ` cvs-commit at gcc dot gnu.org 2022-10-23 19:59 ` cvs-commit at gcc dot gnu.org [this message] 2022-10-23 20:17 ` 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-105633-4-iJFwFTI5LD@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).