public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/104618] New: [12 Regression] trunk 20220221 on x86_64-linux-gnu ICEs building sh.cc for sh4-linux-gnu
Date: Mon, 21 Feb 2022 19:22:20 +0000	[thread overview]
Message-ID: <bug-104618-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104618

            Bug ID: 104618
           Summary: [12 Regression] trunk 20220221 on x86_64-linux-gnu
                    ICEs building sh.cc for sh4-linux-gnu
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: doko at debian dot org
  Target Milestone: ---

Created attachment 52484
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52484&action=edit
preprocessed source

seen with trunk 20220221, building a cross compiler on x86_64-linux-gnu:

../../src/gcc/config/sh/sh.cc: In function 'void output_stack_adjust(int, rtx,
int, HARD_REG_SET*, bool)':
../../src/gcc/config/sh/sh.cc:6813:40: internal compiler error: in
build_call_a, at cp/call.cc:381
 6813 |               insn = emit_fn (GEN_SUB3 (reg, reg, const_reg));
      |                                        ^

0x65712f build_call_a(tree_node*, int, tree_node**)
        ../../src/gcc/cp/call.cc:381
0x6a3d30 build_cxx_call(tree_node*, int, tree_node**, int, tree_node*)
        ../../src/gcc/cp/call.cc:10379
0x8752fc cp_build_function_call_vec(tree_node*, vec<tree_node*, va_gc,
vl_embed>**, int, tree_node*)
        ../../src/gcc/cp/typeck.cc:4285
0x83bf3e finish_call_expr(tree_node*, vec<tree_node*, va_gc, vl_embed>**, bool,
bool, int)
        ../../src/gcc/cp/semantics.cc:2895
0x7ca0fa cp_parser_postfix_expression
        ../../src/gcc/cp/parser.cc:7878
0x7b3b2a cp_parser_binary_expression
        ../../src/gcc/cp/parser.cc:10041
0x7b434e cp_parser_assignment_expression
        ../../src/gcc/cp/parser.cc:10345
0x7b7e37 cp_parser_parenthesized_expression_list_elt
        ../../src/gcc/cp/parser.cc:7986
0x7b7f80 cp_parser_parenthesized_expression_list
        ../../src/gcc/cp/parser.cc:8468
0x7ca016 cp_parser_postfix_expression
        ../../src/gcc/cp/parser.cc:7729
0x7b3b2a cp_parser_binary_expression
        ../../src/gcc/cp/parser.cc:10041
0x7b434e cp_parser_assignment_expression
        ../../src/gcc/cp/parser.cc:10345
0x7b5ea9 cp_parser_constant_expression
        ../../src/gcc/cp/parser.cc:10648
0x7b5f41 cp_parser_initializer_clause
        ../../src/gcc/cp/parser.cc:25216
0x7b4528 cp_parser_assignment_expression
        ../../src/gcc/cp/parser.cc:10365
0x7b5609 cp_parser_expression
        ../../src/gcc/cp/parser.cc:10515
0x7b8667 cp_parser_expression_statement
        ../../src/gcc/cp/parser.cc:12711
0x7c501a cp_parser_statement
        ../../src/gcc/cp/parser.cc:12507
0x7c610d cp_parser_statement_seq_opt
        ../../src/gcc/cp/parser.cc:12856
0x7c61bf cp_parser_compound_statement
        ../../src/gcc/cp/parser.cc:12808
Please submit a full bug report, with preprocessed source (by using
-freport-bug).

             reply	other threads:[~2022-02-21 19:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21 19:22 doko at debian dot org [this message]
2022-02-21 21:06 ` [Bug c++/104618] [12 Regression] trunk 20220221 on x86_64-linux-gnu ICEs building sh.cc for sh4-linux-gnu (in build_call_a, at cp/call.cc:381) pinskia at gcc dot gnu.org
2022-02-21 23:32 ` pinskia at gcc dot gnu.org
2022-02-22  0:29 ` pinskia at gcc dot gnu.org
2022-02-22 10:29 ` rguenth at gcc dot gnu.org
2022-02-25 19:21 ` jason at gcc dot gnu.org
2022-02-27 22:52 ` cvs-commit at gcc dot gnu.org
2022-03-02 20:57 ` mpolacek at gcc dot gnu.org
2022-03-07 23:32 ` cvs-commit at gcc dot gnu.org
2022-03-08  3:59 ` jason 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-104618-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: link
Be 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).