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/101101] ICE in gfc_build_array_type, at fortran/trans-types.c:1391 Date: Wed, 26 Jan 2022 17:23:02 +0000 [thread overview] Message-ID: <bug-101101-4-vayj7qW86z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101101-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101101 --- Comment #2 from G. Steinmetz <gscfq@t-online.de> --- Alternatives : $ cat zz1.f90 program p class(*), pointer :: x dimension :: x(:) end $ cat zz2.f90 program p class(*) :: x(:) pointer :: x end $ gfortran-12-20220123 -c zz1.f90 f951: internal compiler error: Segmentation fault 0xcc430f crash_signal ../../gcc/toplev.cc:322 0x672cc7 resolve_fl_var_and_proc ../../gcc/fortran/resolve.cc:12866 0x76ace6 resolve_fl_variable ../../gcc/fortran/resolve.cc:13012 0x76ace6 resolve_symbol ../../gcc/fortran/resolve.cc:16096 0x789642 do_traverse_symtree ../../gcc/fortran/symbol.cc:4174 0x76d9c4 resolve_types ../../gcc/fortran/resolve.cc:17455 0x768e5c gfc_resolve(gfc_namespace*) ../../gcc/fortran/resolve.cc:17570 0x751194 resolve_all_program_units ../../gcc/fortran/parse.cc:6586 0x751194 gfc_parse_file() ../../gcc/fortran/parse.cc:6842 0x79e86f gfc_be_parse_file ../../gcc/fortran/f95-lang.cc:216 $ gfortran-12-20220123 -c zz2.f90 zz2.f90:4:3: 4 | end | 1 internal compiler error: Segmentation fault 0xcc430f crash_signal ../../gcc/toplev.cc:322 0x6ee9b1 free_expr0 ../../gcc/fortran/expr.cc:446 0x6eeb18 gfc_free_expr(gfc_expr*) ../../gcc/fortran/expr.cc:530 0x6b9fce gfc_free_array_spec(gfc_array_spec*) ../../gcc/fortran/array.cc:352 0x78fd1f free_components ../../gcc/fortran/symbol.cc:2606 0x78fd1f gfc_free_symbol(gfc_symbol*&) ../../gcc/fortran/symbol.cc:3078 0x78fe79 gfc_release_symbol(gfc_symbol*&) ../../gcc/fortran/symbol.cc:3127 0x78ff4e free_sym_tree ../../gcc/fortran/symbol.cc:3904 0x78ff3c free_sym_tree ../../gcc/fortran/symbol.cc:3901 0x78faf0 gfc_free_namespace(gfc_namespace*&) ../../gcc/fortran/symbol.cc:4043 0x790209 gfc_symbol_done_2() ../../gcc/fortran/symbol.cc:4105 0x728008 gfc_done_2() ../../gcc/fortran/misc.cc:382 0x751818 translate_all_program_units ../../gcc/fortran/parse.cc:6670 0x751818 gfc_parse_file() ../../gcc/fortran/parse.cc:6938 0x79e86f gfc_be_parse_file ../../gcc/fortran/f95-lang.cc:216
next prev parent reply other threads:[~2022-01-26 17:23 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-16 17:23 [Bug fortran/101101] New: " gscfq@t-online.de 2021-07-29 20:07 ` [Bug fortran/101101] " anlauf at gcc dot gnu.org 2022-01-26 17:23 ` gscfq@t-online.de [this message] 2023-03-06 17:15 ` 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-101101-4-vayj7qW86z@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).