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/97455] ICE on invalid code (wrong pointer assignment) in SELECT TYPE construct Date: Wed, 31 Mar 2021 17:28:10 +0000 [thread overview] Message-ID: <bug-97455-4-tVhRgF0zou@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97455-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97455 G. Steinmetz <gscfq@t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gscfq@t-online.de --- Comment #2 from G. Steinmetz <gscfq@t-online.de> --- Update, backtrace and a variation : $ cat z1.f90 subroutine s select type (x => x(:)) end select end $ cat z2.f90 subroutine s select type (x ==> x) end select end $ gfortran-11-20210328 -c z1.f90 f951: internal compiler error: Segmentation fault 0xc09d4f crash_signal ../../gcc/toplev.c:327 0x6576ba delete_root ../../gcc/fortran/bbt.c:150 0x65787e gfc_delete_bbt(void*, void*, int (*)(void*, void*)) ../../gcc/fortran/bbt.c:197 0x7224d8 gfc_delete_symtree(gfc_symtree**, char const*) ../../gcc/fortran/symbol.c:2962 0x723bd6 gfc_restore_last_undo_checkpoint() ../../gcc/fortran/symbol.c:3706 0x6dab47 reject_statement ../../gcc/fortran/parse.c:2678 0x6de324 match_word ../../gcc/fortran/parse.c:70 0x6de324 decode_statement ../../gcc/fortran/parse.c:428 0x6dfb3c next_free ../../gcc/fortran/parse.c:1316 0x6dfb3c next_statement ../../gcc/fortran/parse.c:1548 0x6e1f04 parse_spec ../../gcc/fortran/parse.c:3783 0x6e3f7c parse_progunit ../../gcc/fortran/parse.c:5896 0x6e5a20 gfc_parse_file() ../../gcc/fortran/parse.c:6444 0x7320ef gfc_be_parse_file ../../gcc/fortran/f95-lang.c:212
prev parent reply other threads:[~2021-03-31 17:28 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-16 8:16 [Bug fortran/97455] New: " federico.perini at gmail dot com 2020-12-12 19:06 ` [Bug fortran/97455] " dominiq at lps dot ens.fr 2021-03-31 17:28 ` gscfq@t-online.de [this message]
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-97455-4-tVhRgF0zou@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).