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/106999] New: [11/12/13 Regression] ICE tree check: expected record_type or union_type or qual_union_type, have function_type in gfc_class_data_get, at fortran/trans-expr.cc:233 Date: Wed, 21 Sep 2022 17:32:27 +0000 [thread overview] Message-ID: <bug-106999-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106999 Bug ID: 106999 Summary: [11/12/13 Regression] ICE tree check: expected record_type or union_type or qual_union_type, have function_type in gfc_class_data_get, at fortran/trans-expr.cc:233 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Started with r11 before 20200503 : $ cat z1.f90 program p type t procedure(g), pointer :: f end type class(t), allocatable :: z call s(z%f) contains subroutine g(x) class(t) :: x end subroutine s(x) class(*) :: x end end $ gfortran-13-20220918 -c z1.f90 $ gfortran-10 -c z1.f90 $ gfortran-10 -c z1.f90 -fcheck=all $ $ gfortran-13-20220918 -c z1.f90 -fcheck=all z1.f90:6:14: 6 | call s(z%f) | 1 internal compiler error: tree check: expected record_type or union_type or qual_union_type, have function_type in gfc_class_data_get, at fortran/trans-expr.cc:233 0x6c055a tree_check_failed(tree_node const*, char const*, int, char const*, ...) ../../gcc/tree.cc:8827 0x8ec48b tree_check3(tree_node*, char const*, int, char const*, tree_code, tree_code, tree_code) ../../gcc/tree.h:3560 0x8ec48b gfc_class_data_get(tree_node*) ../../gcc/fortran/trans-expr.cc:233 0x8f6b46 gfc_conv_procedure_call(gfc_se*, gfc_symbol*, gfc_actual_arglist*, gfc_expr*, vec<tree_node*, va_gc, vl_embed>*) ../../gcc/fortran/trans-expr.cc:7228 0x9580b0 gfc_trans_call(gfc_code*, bool, tree_node*, tree_node*, bool) ../../gcc/fortran/trans-stmt.cc:422 0x8b0aa6 trans_code ../../gcc/fortran/trans.cc:2018 0x8e8009 gfc_generate_function_code(gfc_namespace*) ../../gcc/fortran/trans-decl.cc:7654 0x859a2e translate_all_program_units ../../gcc/fortran/parse.cc:6671 0x859a2e gfc_parse_file() ../../gcc/fortran/parse.cc:6977 0x8a7ccf gfc_be_parse_file ../../gcc/fortran/f95-lang.cc:229
next reply other threads:[~2022-09-21 17:32 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-21 17:32 gscfq@t-online.de [this message] 2022-09-21 17:32 ` [Bug fortran/106999] " gscfq@t-online.de 2022-09-22 6:48 ` rguenth at gcc dot gnu.org 2022-09-22 19:22 ` marxin at gcc dot gnu.org 2023-04-17 19:42 ` [Bug fortran/106999] [11/12/13/14 " anlauf at gcc dot gnu.org 2023-05-29 10:07 ` jakub at gcc dot gnu.org 2024-03-31 12:16 ` pault at gcc dot gnu.org 2024-04-02 14:53 ` cvs-commit at gcc dot gnu.org 2024-04-23 9:49 ` [Bug fortran/106999] [11/12/13 " pault at gcc dot gnu.org 2024-05-06 9:57 ` cvs-commit at gcc dot gnu.org 2024-05-06 10:01 ` cvs-commit at gcc dot gnu.org 2024-05-06 10:03 ` pault 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-106999-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).