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/100275] ICE in gfc_build_null_descriptor, at fortran/trans-array.c:417 Date: Mon, 26 Apr 2021 19:52:12 +0000 [thread overview] Message-ID: <bug-100275-4-tZoInyhB32@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100275-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100275 G. Steinmetz <gscfq@t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-invalid-code --- Comment #1 from G. Steinmetz <gscfq@t-online.de> --- Additional variants : $ cat z2.f90 program p type t integer :: a end type type(t) :: x data x /t(null())/ end $ cat z3.f90 program p type t integer :: a(1) end type type(t) :: z data z /t(f())/ end $ gfortran-11-20210425 -c z2.f90 # detected z2.f90:6:13: 6 | data x /t(null())/ | 1 Error: non-constant initialization expression at (1) $ gfortran-11-20210425 -c z3.f90 z3.f90:1:9: 1 | program p | 1 internal compiler error: in gfc_conv_array_initializer, at fortran/trans-array.c:6230 0x785ae2 gfc_conv_array_initializer(tree_node*, gfc_expr*) ../../gcc/fortran/trans-array.c:6230 0x7c6d20 gfc_conv_initializer(gfc_expr*, gfc_typespec*, tree_node*, bool, bool, bool) ../../gcc/fortran/trans-expr.c:7948 0x7c74b3 gfc_conv_structure(gfc_se*, gfc_expr*, int) ../../gcc/fortran/trans-expr.c:8863 0x7c6e79 gfc_conv_initializer(gfc_expr*, gfc_typespec*, tree_node*, bool, bool, bool) ../../gcc/fortran/trans-expr.c:7983 0x7a756a gfc_get_symbol_decl(gfc_symbol*) ../../gcc/fortran/trans-decl.c:1918 0x7ab08f generate_local_decl ../../gcc/fortran/trans-decl.c:5955 0x75b472 do_traverse_symtree ../../gcc/fortran/symbol.c:4170 0x7ac5cc generate_local_vars ../../gcc/fortran/trans-decl.c:6161 0x7ac5cc gfc_generate_function_code(gfc_namespace*) ../../gcc/fortran/trans-decl.c:6820 0x723fa6 translate_all_program_units ../../gcc/fortran/parse.c:6355 0x723fa6 gfc_parse_file() ../../gcc/fortran/parse.c:6624 0x770e5f gfc_be_parse_file ../../gcc/fortran/f95-lang.c:212
next prev parent reply other threads:[~2021-04-26 19:52 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-26 19:51 [Bug fortran/100275] New: " gscfq@t-online.de 2021-04-26 19:52 ` gscfq@t-online.de [this message] 2021-04-29 20:57 ` [Bug fortran/100275] " anlauf at gcc dot gnu.org 2022-01-25 18:08 ` gscfq@t-online.de 2022-01-25 18:25 ` 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-100275-4-tZoInyhB32@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).