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 c++/107383] New: [13 Regression] ICE in cp_build_binary_op, at cp/typeck.cc:6181 Date: Mon, 24 Oct 2022 17:55:59 +0000 [thread overview] Message-ID: <bug-107383-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107383 Bug ID: 107383 Summary: [13 Regression] ICE in cp_build_binary_op, at cp/typeck.cc:6181 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Started between 20221009 and 20221016, with file gcc.dg/pr69627.c : $ cat z1.cc void foo () { float t[2] = { 1, 2 }; int const *s = 0; t[1] / s; } void bar () { float t[2] = { 1, 2 }; int const *s[2] = { 0, 0 }; t[1] / s[0]; } $ g++-13-20221023 -c z1.cc -m32 -std=c++0x z1.cc: In function 'void foo()': z1.cc:6:10: internal compiler error: in cp_build_binary_op, at cp/typeck.cc:6181 6 | t[1] / s; | ^ 0xb45e49 cp_build_binary_op(op_location_t const&, tree_code, tree_node*, tree_node*, int) ../../gcc/cp/typeck.cc:6181 0x81f755 build_new_op(op_location_t const&, tree_code, int, tree_node*, tree_node*, tree_node*, tree_node*, tree_node**, int) ../../gcc/cp/call.cc:7094 0xb2e48d build_x_binary_op(op_location_t const&, tree_code, tree_node*, tree_code, tree_node*, tree_code, tree_node*, tree_node**, int) ../../gcc/cp/typeck.cc:4722 0x9ec893 cp_parser_binary_expression ../../gcc/cp/parser.cc:10266 0x9ed404 cp_parser_assignment_expression ../../gcc/cp/parser.cc:10427 0x9efa02 cp_parser_expression ../../gcc/cp/parser.cc:10597 0x9f3b87 cp_parser_expression_statement ../../gcc/cp/parser.cc:12702 0xa03a44 cp_parser_statement ../../gcc/cp/parser.cc:12491 0xa04c34 cp_parser_statement_seq_opt ../../gcc/cp/parser.cc:12853 0xa04d17 cp_parser_compound_statement ../../gcc/cp/parser.cc:12805 0xa2d220 cp_parser_function_body ../../gcc/cp/parser.cc:25179 0xa2d220 cp_parser_ctor_initializer_opt_and_function_body ../../gcc/cp/parser.cc:25230 0xa2d89a cp_parser_function_definition_after_declarator ../../gcc/cp/parser.cc:31387 0xa2eddc cp_parser_function_definition_from_specifiers_and_declarator ../../gcc/cp/parser.cc:31304 0xa2eddc cp_parser_init_declarator ../../gcc/cp/parser.cc:22633 0xa01892 cp_parser_simple_declaration ../../gcc/cp/parser.cc:15284 0xa3679b cp_parser_declaration ../../gcc/cp/parser.cc:14970 0xa372b8 cp_parser_translation_unit ../../gcc/cp/parser.cc:5076 0xa372b8 c_parse_file() ../../gcc/cp/parser.cc:48856 0xbcfb01 c_common_parse_file() ../../gcc/c-family/c-opts.cc:1247
next reply other threads:[~2022-10-24 17:56 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-24 17:55 gscfq@t-online.de [this message] 2022-10-24 18:02 ` [Bug c++/107383] " pinskia at gcc dot gnu.org 2022-10-25 6:59 ` rguenth at gcc dot gnu.org 2022-10-25 18:03 ` jakub at gcc dot gnu.org 2022-10-25 18:07 ` jakub at gcc dot gnu.org 2022-10-27 8:27 ` cvs-commit at gcc dot gnu.org 2022-10-27 8:28 ` jakub 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-107383-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).