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/104849] ICE in find_array_section, at fortran/expr.cc:1616
Date: Mon, 16 May 2022 19:11:50 +0000	[thread overview]
Message-ID: <bug-104849-4-R5plZ1QUll@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104849-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104849

--- Comment #4 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:50c73234630d51e7d66986710afd1af23851002b

commit r11-10006-g50c73234630d51e7d66986710afd1af23851002b
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Wed Mar 9 21:58:26 2022 +0100

    Fortran: improve error recovery on invalid array section

    gcc/fortran/ChangeLog:

            PR fortran/104849
            * expr.c (find_array_section): Avoid NULL pointer dereference on
            invalid array section.

    gcc/testsuite/ChangeLog:

            PR fortran/104849
            * gfortran.dg/pr104849.f90: New test.

    (cherry picked from commit 22015e77d3e45306077396b9de8a8a28bb67fb20)

  parent reply	other threads:[~2022-05-16 19:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08 20:01 [Bug fortran/104849] New: " gscfq@t-online.de
2022-03-09 20:31 ` [Bug fortran/104849] " anlauf at gcc dot gnu.org
2022-03-09 20:59 ` cvs-commit at gcc dot gnu.org
2022-03-09 21:05 ` anlauf at gcc dot gnu.org
2022-05-16 19:11 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-16 19:40 ` cvs-commit at gcc dot gnu.org
2022-05-16 20:05 ` 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-104849-4-R5plZ1QUll@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: link
Be 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).