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/104430] New: [9/10/11/12 Regression] ICE in gfc_conv_component_ref, at fortran/trans-expr.cc:2742 Date: Mon, 07 Feb 2022 18:49:37 +0000 [thread overview] Message-ID: <bug-104430-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104430 Bug ID: 104430 Summary: [9/10/11/12 Regression] ICE in gfc_conv_component_ref, at fortran/trans-expr.cc:2742 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: --- Starts with r8, basically r9 changed between 20181014 and 20181021 : $ cat z1.f90 module m type t integer :: a end type contains function f(x) result(z) class(t) :: x(:) type(t) :: z(size(x%a)) end end program p use m class(t), allocatable :: y(:), z(:) z = f(y) end $ gfortran-7 -c z1.f90 $ $ gfortran-12-20220206 -c z1.f90 z1.f90:14:11: 14 | z = f(y) | 1 internal compiler error: Segmentation fault 0xe6fc6f crash_signal ../../gcc/toplev.cc:322 0x8265df tree_check3(tree_node*, char const*, int, char const*, tree_code, tree_code, tree_code) ../../gcc/tree.h:3483 0x8265df gfc_conv_component_ref(gfc_se*, gfc_ref*) ../../gcc/fortran/trans-expr.cc:2742 0x837897 gfc_conv_variable ../../gcc/fortran/trans-expr.cc:3118 0x83264a gfc_conv_expr(gfc_se*, gfc_expr*) ../../gcc/fortran/trans-expr.cc:9406 0x835760 gfc_conv_expr_lhs(gfc_se*, gfc_expr*) ../../gcc/fortran/trans-expr.cc:9436 0x7f0858 gfc_conv_ss_descriptor ../../gcc/fortran/trans-array.cc:3219 0x7fd2e5 gfc_conv_expr_descriptor(gfc_se*, gfc_expr*) ../../gcc/fortran/trans-array.cc:7494 0x8462cf gfc_conv_intrinsic_size ../../gcc/fortran/trans-intrinsic.cc:7975 0x86295b gfc_conv_intrinsic_function(gfc_se*, gfc_expr*) ../../gcc/fortran/trans-intrinsic.cc:10644 0x83262a gfc_conv_expr(gfc_se*, gfc_expr*) ../../gcc/fortran/trans-expr.cc:9398 0x834b5a gfc_apply_interface_mapping(gfc_interface_mapping*, gfc_se*, gfc_expr*) ../../gcc/fortran/trans-expr.cc:4865 0x7ee747 gfc_set_loop_bounds_from_array_spec(gfc_interface_mapping*, gfc_se*, gfc_array_spec*) ../../gcc/fortran/trans-array.cc:1080 0x83066f 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:7472 0x8426ac gfc_trans_arrayfunc_assign ../../gcc/fortran/trans-expr.cc:10873 0x8428d4 gfc_trans_assignment(gfc_expr*, gfc_expr*, bool, bool, bool, bool) ../../gcc/fortran/trans-expr.cc:12038 0x7e9887 trans_code ../../gcc/fortran/trans.cc:1916 0x8207a9 gfc_generate_function_code(gfc_namespace*) ../../gcc/fortran/trans-decl.cc:7654 0x7931fe translate_all_program_units ../../gcc/fortran/parse.cc:6651 0x7931fe gfc_parse_file() ../../gcc/fortran/parse.cc:6938
next reply other threads:[~2022-02-07 18:49 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-07 18:49 gscfq@t-online.de [this message] 2022-02-08 9:04 ` [Bug fortran/104430] " rguenth at gcc dot gnu.org 2022-02-24 10:44 ` [Bug fortran/104430] [9/10/11/12 Regression] ICE in gfc_conv_component_ref, at fortran/trans-expr.cc:2742 since r9-3522-gd0477233215e37de marxin at gcc dot gnu.org 2022-03-07 21:12 ` cvs-commit at gcc dot gnu.org 2022-03-19 7:49 ` cvs-commit at gcc dot gnu.org 2022-05-27 9:47 ` [Bug fortran/104430] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-27 19:55 ` [Bug fortran/104430] [10 " anlauf at gcc dot gnu.org 2022-06-28 10:48 ` jakub at gcc dot gnu.org 2022-08-26 10:59 ` redi at gcc dot gnu.org 2022-08-26 11:04 ` redi at gcc dot gnu.org 2023-06-02 8:52 ` 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-104430-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).