public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gscfq@t-online.de" <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 17:54:21 +0000 [thread overview] Message-ID: <bug-95980-4-9v9NlQ2bWw@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 G. Steinmetz <gscfq@t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-invalid-code --- Comment #1 from G. Steinmetz <gscfq@t-online.de> --- Related (and presumably also pr86551) : $ cat z2.f90 program p type t end type class(t) :: x select type (y => x) end select end $ gfortran-11-20200628 -c z2.f90 f951: internal compiler error: Segmentation fault 0xbd215f crash_signal ../../gcc/toplev.c:328 0x686d9b copy_ts_from_selector_to_associate ../../gcc/fortran/match.c:6162 0x68f543 gfc_match_select_type() ../../gcc/fortran/match.c:6422 0x6ae2b4 match_word ../../gcc/fortran/parse.c:65 0x6ae2b4 decode_statement ../../gcc/fortran/parse.c:428 0x6afaea next_free ../../gcc/fortran/parse.c:1280 0x6afaea next_statement ../../gcc/fortran/parse.c:1512 0x6b113b parse_spec ../../gcc/fortran/parse.c:3923 0x6b3f0c parse_progunit ../../gcc/fortran/parse.c:5852 0x6b55e9 gfc_parse_file() ../../gcc/fortran/parse.c:6393 0x7016ff gfc_be_parse_file ../../gcc/fortran/f95-lang.c:212
next prev parent reply other threads:[~2020-06-29 17:54 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 ` gscfq@t-online.de [this message] 2020-06-29 18:38 ` [Bug fortran/95980] " 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 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-9v9NlQ2bWw@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: linkBe 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).