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/95980] ICE in get_unique_type_string, at fortran/class.c:485
Date: Thu, 23 Jul 2020 20:07:55 +0000 [thread overview]
Message-ID: <bug-95980-4-TqUp2HRogP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95980-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95980
--- Comment #19 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:76a8ff3948ad5a36ccae7305a2e9a7c2499418e5
commit r10-8526-g76a8ff3948ad5a36ccae7305a2e9a7c2499418e5
Author: Harald Anlauf <anlauf@gmx.de>
Date: Fri Jul 10 21:35:35 2020 +0200
PR fortran/95980 - ICE in get_unique_type_string, at fortran/class.c:485
In SELECT TYPE, the argument may be an incorrectly specified unlimited
CLASS variable. Avoid NULL pointer dereferences for clean error
recovery.
gcc/fortran/
PR fortran/95980
* class.c (gfc_add_component_ref, gfc_build_class_symbol):
Add checks for NULL pointer dereference.
* primary.c (gfc_variable_attr): Likewise.
* resolve.c (resolve_variable, resolve_assoc_var)
(resolve_fl_var_and_proc, resolve_fl_variable_derived)
(resolve_symbol): Likewise.
(cherry picked from commit 70c884a4b82733027ac0e2620d09169b177080d7)
next prev parent reply other threads:[~2020-07-23 20:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 17:53 [Bug fortran/95980] New: " gscfq@t-online.de
2020-06-29 17:54 ` [Bug fortran/95980] " gscfq@t-online.de
2020-06-29 18:38 ` kargl at gcc dot gnu.org
2020-06-29 18:51 ` kargl at gcc dot gnu.org
2020-06-29 20:59 ` anlauf at gcc dot gnu.org
2020-07-06 17:01 ` cvs-commit at gcc dot gnu.org
2020-07-06 18:01 ` dominiq at lps dot ens.fr
2020-07-06 20:25 ` anlauf at gcc dot gnu.org
2020-07-06 20:29 ` anlauf at gcc dot gnu.org
2020-07-06 21:24 ` dominiq at lps dot ens.fr
2020-07-06 21:57 ` sgk at troutmask dot apl.washington.edu
2020-07-06 22:38 ` dominiq at lps dot ens.fr
2020-07-07 6:29 ` anlauf at gcc dot gnu.org
2020-07-07 6:32 ` anlauf at gcc dot gnu.org
2020-07-07 7:35 ` dominiq at lps dot ens.fr
2020-07-07 17:26 ` gscfq@t-online.de
2020-07-07 21:03 ` anlauf at gcc dot gnu.org
2020-07-08 5:49 ` gscfq@t-online.de
2020-07-10 19:36 ` cvs-commit at gcc dot gnu.org
2020-07-23 20:07 ` cvs-commit at gcc dot gnu.org
2020-07-23 20:07 ` cvs-commit at gcc dot gnu.org [this message]
2020-07-24 20:56 ` 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-95980-4-TqUp2HRogP@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).