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/108434] [12/13 Regression] ICE in class_allocatable, at fortran/expr.cc:5000
Date: Thu, 19 Jan 2023 18:23:27 +0000	[thread overview]
Message-ID: <bug-108434-4-5X3r8hkgkv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108434-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 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:117848f425a3c0eda85517b4bdaf2ebe3bc705c2

commit r13-5260-g117848f425a3c0eda85517b4bdaf2ebe3bc705c2
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Wed Jan 18 22:13:29 2023 +0100

    Fortran: error recovery for invalid CLASS component [PR108434]

    gcc/fortran/ChangeLog:

            PR fortran/108434
            * expr.cc (class_allocatable): Prevent NULL pointer dereference
            or invalid read.
            (class_pointer): Likewise.

    gcc/testsuite/ChangeLog:

            PR fortran/108434
            * gfortran.dg/pr108434.f90: New test.

  parent reply	other threads:[~2023-01-19 18:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-17 17:45 [Bug fortran/108434] New: " gscfq@t-online.de
2023-01-17 20:01 ` [Bug fortran/108434] " anlauf at gcc dot gnu.org
2023-01-18  8:46 ` marxin at gcc dot gnu.org
2023-01-18  8:58 ` rguenth at gcc dot gnu.org
2023-01-18 21:21 ` anlauf at gcc dot gnu.org
2023-01-19 18:23 ` cvs-commit at gcc dot gnu.org [this message]
2023-01-23 21:30 ` cvs-commit at gcc dot gnu.org
2023-01-23 21:39 ` anlauf at gcc dot gnu.org
2023-03-19 21:23 ` anlauf at gcc dot gnu.org
2023-05-08 12:26 ` [Bug fortran/108434] [12/13/14 " rguenth 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-108434-4-5X3r8hkgkv@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).