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/103717] ICE in doloop_code, at fortran/frontend-passes.c:2656
Date: Thu, 16 Dec 2021 22:22:49 +0000	[thread overview]
Message-ID: <bug-103717-4-9pK7zaQxqH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103717-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:

https://gcc.gnu.org/g:b99da5f23e122af800c1fca77e03664e686ae575

commit r10-10343-gb99da5f23e122af800c1fca77e03664e686ae575
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Tue Dec 14 21:57:04 2021 +0100

    Fortran: prevent NULL pointer dereference in check of passed do-loop
variable

    gcc/fortran/ChangeLog:

            PR fortran/103717
            * frontend-passes.c (doloop_code): Prevent NULL pointer
            dereference when checking for passing a do-loop variable to a
            contained procedure with an interface mismatch.

    gcc/testsuite/ChangeLog:

            PR fortran/103717
            * gfortran.dg/do_check_19.f90: New test.

    (cherry picked from commit ca39102e10643a6b3f07d06934cc0907ba83d9ee)

  parent reply	other threads:[~2021-12-16 22:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14 18:12 [Bug fortran/103717] New: " gscfq@t-online.de
2021-12-14 20:13 ` [Bug fortran/103717] " anlauf at gcc dot gnu.org
2021-12-14 20:57 ` cvs-commit at gcc dot gnu.org
2021-12-14 21:04 ` anlauf at gcc dot gnu.org
2021-12-15 19:36 ` cvs-commit at gcc dot gnu.org
2021-12-16 22:22 ` cvs-commit at gcc dot gnu.org [this message]
2021-12-16 22:34 ` cvs-commit at gcc dot gnu.org
2021-12-16 22:36 ` 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-103717-4-9pK7zaQxqH@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).