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/105230] [9/10/11/12/13 Regression] ICE in find_array_section, at fortran/expr.cc:1634 Date: Wed, 11 May 2022 17:44:41 +0000 [thread overview] Message-ID: <bug-105230-4-MaeGI8cVwh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105230-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105230 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>: https://gcc.gnu.org/g:0acdbe29f66017fc5cca40dcbd72a0dd41491d07 commit r13-330-g0acdbe29f66017fc5cca40dcbd72a0dd41491d07 Author: Harald Anlauf <anlauf@gmx.de> Date: Tue May 10 23:41:57 2022 +0200 Fortran: fix error recovery on invalid array section gcc/fortran/ChangeLog: PR fortran/105230 * expr.cc (find_array_section): Correct logic to avoid NULL pointer dereference on invalid array section. gcc/testsuite/ChangeLog: PR fortran/105230 * gfortran.dg/pr105230.f90: New test. Co-authored-by: Steven G. Kargl <kargl@gcc.gnu.org>
next prev parent reply other threads:[~2022-05-11 17:44 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-11 16:57 [Bug fortran/105230] New: [9/10/11/12 " gscfq@t-online.de 2022-04-11 17:47 ` [Bug fortran/105230] " kargl at gcc dot gnu.org 2022-04-12 7:43 ` rguenth at gcc dot gnu.org 2022-05-10 19:02 ` [Bug fortran/105230] [9/10/11/12/13 " anlauf at gcc dot gnu.org 2022-05-11 17:44 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-13 19:35 ` cvs-commit at gcc dot gnu.org 2022-05-16 19:11 ` cvs-commit at gcc dot gnu.org 2022-05-16 19:40 ` cvs-commit at gcc dot gnu.org 2022-05-16 20:05 ` cvs-commit at gcc dot gnu.org 2022-05-16 20:07 ` 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-105230-4-MaeGI8cVwh@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).