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/101348] New: ICE in gfc_get_nodesc_array_type, at fortran/trans-types.c:1697 Date: Tue, 06 Jul 2021 17:31:04 +0000 [thread overview] Message-ID: <bug-101348-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101348 Bug ID: 101348 Summary: ICE in gfc_get_nodesc_array_type, at fortran/trans-types.c:1697 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Affects versions down to at least r5 : $ cat z1.f90 module m integer :: a(1)[1:,:] end $ cat z2.f90 program p integer :: a(1)[1:,:] end $ gfortran-12-20210704 -c z2.f90 -fcoarray=lib # accepted $ $ gfortran-12-20210704 -c z1.f90 -fcoarray=lib f951: internal compiler error: Segmentation fault 0xc93c2f crash_signal ../../gcc/toplev.c:328 0x82bedc gfc_get_nodesc_array_type(tree_node*, gfc_array_spec*, gfc_packed, bool) ../../gcc/fortran/trans-types.c:1697 0x7cf376 gfc_get_symbol_decl(gfc_symbol*) ../../gcc/fortran/trans-decl.c:1797 0x7d25c8 gfc_create_module_variable ../../gcc/fortran/trans-decl.c:5359 0x790e12 do_traverse_symtree ../../gcc/fortran/symbol.c:4170 0x7d2dcb gfc_generate_module_vars(gfc_namespace*) ../../gcc/fortran/trans-decl.c:5858 0x7ad0d4 gfc_generate_module_code(gfc_namespace*) ../../gcc/fortran/trans.c:2303 0x759421 translate_all_program_units ../../gcc/fortran/parse.c:6451 0x759421 gfc_parse_file() ../../gcc/fortran/parse.c:6733 0x7a5c4f gfc_be_parse_file ../../gcc/fortran/f95-lang.c:216
next reply other threads:[~2021-07-06 17:31 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-06 17:31 gscfq@t-online.de [this message] 2021-07-18 20:03 ` [Bug fortran/101348] [Coarray] " 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-101348-4@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).