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/106047] ICE in structure_alloc_comps, at fortran/trans-array.cc:9574 Date: Fri, 24 Jun 2022 06:12:21 +0000 [thread overview] Message-ID: <bug-106047-4-hYzff8PWxf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106047-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106047 G. Steinmetz <gscfq@t-online.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|ice-on-invalid-code |ice-on-valid-code --- Comment #3 from G. Steinmetz <gscfq@t-online.de> --- Regarding these variants, all of them actually work : $ cat zc1.f90 program p type t integer, allocatable :: c end type type(t) :: x integer :: n = storage_size(x) print *, n end $ cat zc2.f90 program p type t logical, allocatable :: c end type type(t) :: x integer :: n = storage_size(x) print *, n end $ cat zc3.f90 program p type t real, allocatable :: c end type type(t) :: x integer :: n = storage_size(x) print *, n end $ cat zc4.f90 program p type t character, allocatable :: c end type type(t) :: x integer :: n = storage_size(x) print *, n end $ cat zc5.f90 program p type t class(*), allocatable :: c end type type(t) :: x integer :: n = storage_size(x) print *, n end $ gfortran-13-20220619 zc1.f90 ; a.out 64 $ gfortran-13-20220619 zc2.f90 ; a.out 64 $ gfortran-13-20220619 zc3.f90 ; a.out 64 $ gfortran-13-20220619 zc4.f90 ; a.out 64 $ gfortran-13-20220619 zc5.f90 ; a.out 192 --- Testing additional options, there is never an ICE with zc5.f90, but with the other ones e.g. at line 9129 instead of line 9574 : $ gfortran-13-20220619 -c zc1.f90 -fcoarray=single zc1.f90:5:15: 5 | type(t) :: x | 1 internal compiler error: Segmentation fault 0xcd90df crash_signal ../../gcc/toplev.cc:322 0x7c4366 structure_alloc_comps ../../gcc/fortran/trans-array.cc:9129 0x7c7348 gfc_nullify_alloc_comp(gfc_symbol*, tree_node*, int, int) ../../gcc/fortran/trans-array.cc:10149 0x7c7348 gfc_trans_deferred_array(gfc_symbol*, gfc_wrapped_block*) ../../gcc/fortran/trans-array.cc:11206 0x7dabac gfc_trans_deferred_vars(gfc_symbol*, gfc_wrapped_block*) ../../gcc/fortran/trans-decl.cc:4994 0x7dd1a5 gfc_generate_function_code(gfc_namespace*) ../../gcc/fortran/trans-decl.cc:7756 0x75f53e translate_all_program_units ../../gcc/fortran/parse.cc:6669 0x75f53e gfc_parse_file() ../../gcc/fortran/parse.cc:6956 0x7acb6f gfc_be_parse_file ../../gcc/fortran/f95-lang.cc:229
prev parent reply other threads:[~2022-06-24 6:12 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-21 18:49 [Bug fortran/106047] New: " gscfq@t-online.de 2022-06-22 20:44 ` [Bug fortran/106047] " anlauf at gcc dot gnu.org 2022-06-23 15:41 ` gscfq@t-online.de 2022-06-24 6:12 ` 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-106047-4-hYzff8PWxf@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).