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/104210] [11 Regression] ICE in gfc_zero_size_array, at fortran/arith.cc:1685 since r11-1814-gcc9a9229285a26ac Date: Thu, 07 Apr 2022 18:49:52 +0000 [thread overview] Message-ID: <bug-104210-4-Sfnulp8Nn8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104210-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104210 --- Comment #6 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:5de47ab9032b54a3ada986366168121f23a51c55 commit r11-9792-g5de47ab9032b54a3ada986366168121f23a51c55 Author: Harald Anlauf <anlauf@gmx.de> Date: Tue Mar 29 23:33:23 2022 +0200 Fortran: improve error recovery for invalid coarray function declarations gcc/fortran/ChangeLog: PR fortran/104210 * arith.c (eval_intrinsic): Avoid NULL pointer dereference. (gfc_zero_size_array): Likewise. gcc/testsuite/ChangeLog: PR fortran/104210 * gfortran.dg/pr104210.f90: New test. (cherry picked from commit 892c7f03ae63121766a8be48f7e3b672547fd627)
next prev parent reply other threads:[~2022-04-07 18:49 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-24 18:59 [Bug fortran/104210] New: [11/12 Regression] ICE in gfc_zero_size_array, at fortran/arith.cc:1685 gscfq@t-online.de 2022-01-25 7:56 ` [Bug fortran/104210] " rguenth at gcc dot gnu.org 2022-01-25 8:41 ` [Bug fortran/104210] [11/12 Regression] ICE in gfc_zero_size_array, at fortran/arith.cc:1685 since r11-1814-gcc9a9229285a26ac marxin at gcc dot gnu.org 2022-03-29 20:34 ` anlauf at gcc dot gnu.org 2022-03-29 21:42 ` anlauf at gcc dot gnu.org 2022-04-05 17:40 ` cvs-commit at gcc dot gnu.org 2022-04-05 17:43 ` [Bug fortran/104210] [11 " anlauf at gcc dot gnu.org 2022-04-07 18:49 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-07 18:50 ` 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-104210-4-Sfnulp8Nn8@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).