public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/104430] [10 Regression] ICE in gfc_conv_component_ref, at fortran/trans-expr.cc:2742 since r9-3522-gd0477233215e37de Date: Fri, 26 Aug 2022 11:04:18 +0000 [thread overview] Message-ID: <bug-104430-4-ORQsJshgWp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104430-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104430 --- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> --- The ICE for comment 7 looks a little different, so a new test does seem worthwhile: Bad: 539 /home/remote/jwakely/gcc-bisect-objs/f951.r12-7525 ice.f90:7:30: 7 | forall( iix=1:4, iiy=1:4 ) | 1 internal compiler error: Segmentation fault 0x1459b77 crash_signal ../../gcc/toplev.cc:322 0xf22b21 split_tree ../../gcc/fold-const.cc:815 0xf5139c fold_binary_loc(unsigned int, tree_code, tree_node*, tree_node*, tree_node*) ../../gcc/fold-const.cc:11269 0xf5d559 fold_build2_loc(unsigned int, tree_code, tree_node*, tree_node*, tree_node*) ../../gcc/fold-const.cc:13814 0xc21e73 gfc_conv_expr_op ../../gcc/fortran/trans-expr.cc:3921 0xc35f01 gfc_conv_expr(gfc_se*, gfc_expr*) ../../gcc/fortran/trans-expr.cc:9394 0xc36049 gfc_conv_expr_val(gfc_se*, gfc_expr*) ../../gcc/fortran/trans-expr.cc:9451 0xc3f8bf gfc_conv_intrinsic_function_args ../../gcc/fortran/trans-intrinsic.cc:237 0xc3face gfc_conv_intrinsic_conversion ../../gcc/fortran/trans-intrinsic.cc:295 0xc60a8b gfc_conv_intrinsic_function(gfc_se*, gfc_expr*) ../../gcc/fortran/trans-intrinsic.cc:10288 0xc32027 gfc_conv_function_expr ../../gcc/fortran/trans-expr.cc:8258 0xc35f19 gfc_conv_expr(gfc_se*, gfc_expr*) ../../gcc/fortran/trans-expr.cc:9398 0xc3d718 gfc_trans_assignment_1 ../../gcc/fortran/trans-expr.cc:11686 0xc3ead6 gfc_trans_assignment(gfc_expr*, gfc_expr*, bool, bool, bool, bool) ../../gcc/fortran/trans-expr.cc:12077 0xca2aab gfc_trans_forall_1 ../../gcc/fortran/trans-stmt.cc:5192 0xca2eb6 gfc_trans_forall(gfc_code*) ../../gcc/fortran/trans-stmt.cc:5298 0xbca74c trans_code ../../gcc/fortran/trans.cc:2064 0xbcaa4e gfc_trans_code(gfc_code*) ../../gcc/fortran/trans.cc:2268 0xc9b362 gfc_trans_block_construct(gfc_code*) ../../gcc/fortran/trans-stmt.cc:2314 0xbca631 trans_code ../../gcc/fortran/trans.cc:2012 Please submit a full bug report, with preprocessed source (by using -freport-bug). Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions.
next prev parent reply other threads:[~2022-08-26 11:04 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-07 18:49 [Bug fortran/104430] New: [9/10/11/12 Regression] ICE in gfc_conv_component_ref, at fortran/trans-expr.cc:2742 gscfq@t-online.de 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 [this message] 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-ORQsJshgWp@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).