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/95978] [10/11 Regression] ICE in gfc_match_data, at fortran/decl.c:731
Date: Tue, 30 Jun 2020 18:46:52 +0000	[thread overview]
Message-ID: <bug-95978-4-qPjzgyT64n@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95978-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 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:aa0868ffe0fd45891a9596bf4995f1b610243fa6

commit r10-8400-gaa0868ffe0fd45891a9596bf4995f1b610243fa6
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Mon Jun 29 23:20:16 2020 +0200

    PR fortran/95978 - ICE in gfc_match_data, at fortran/decl.c:731

    Catch NULL pointer dereference on invalid DATA statement.

    gcc/fortran/
            PR fortran/95978
            * decl.c (gfc_match_data): Avoid NULL pointer dereference.

    (cherry picked from commit 583812c2e2f3593823622b0a5821d957c832dbd0)

  parent reply	other threads:[~2020-06-30 18:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 17:50 [Bug fortran/95978] New: " gscfq@t-online.de
2020-06-29 20:47 ` [Bug fortran/95978] " dominiq at lps dot ens.fr
2020-06-29 21:05 ` anlauf at gcc dot gnu.org
2020-06-29 21:11 ` anlauf at gcc dot gnu.org
2020-06-29 21:21 ` cvs-commit at gcc dot gnu.org
2020-06-29 21:25 ` anlauf at gcc dot gnu.org
2020-06-30 18:46 ` cvs-commit at gcc dot gnu.org [this message]
2020-06-30 18:48 ` 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-95978-4-qPjzgyT64n@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).