public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kargl 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: Mon, 29 Jun 2020 18:38:25 +0000 [thread overview]
Message-ID: <bug-95980-4-2Gzu4p91qJ@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
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
Priority|P3 |P4
--- Comment #2 from kargl at gcc dot gnu.org ---
Patch is against svn r280156.
Index: gcc/fortran/match.c
===================================================================
--- gcc/fortran/match.c (revision 280157)
+++ gcc/fortran/match.c (working copy)
@@ -6174,7 +6174,10 @@ build_class_sym:
{
/* The correct class container has to be available. */
assoc_sym->ts.type = BT_CLASS;
- assoc_sym->ts.u.derived = CLASS_DATA (selector)->ts.u.derived;
+ if (CLASS_DATA (selector)->ts.u.derived != NULL)
+ assoc_sym->ts.u.derived = CLASS_DATA (selector)->ts.u.derived;
+ else
+ assoc_sym->ts.u.derived = selector->ts.u.derived;
assoc_sym->attr.pointer = 1;
gfc_build_class_symbol (&assoc_sym->ts, &assoc_sym->attr,
&assoc_sym->as);
}
next prev parent reply other threads:[~2020-06-29 18:38 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 [this message]
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
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-2Gzu4p91qJ@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).