public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kito.cheng at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/95683] New: internal compiler error: in riscv_gpr_save_operation_p, at config/riscv/riscv.c:5219
Date: Mon, 15 Jun 2020 14:23:59 +0000	[thread overview]
Message-ID: <bug-95683-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 95683
           Summary: internal compiler error: in
                    riscv_gpr_save_operation_p, at
                    config/riscv/riscv.c:5219
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: kito.cheng at gmail dot com
  Target Milestone: ---
            Target: riscv64-unknown-elf

Report by Pat Pannuto at github:
https://github.com/riscv/riscv-gcc/issues/190

Testcase:

void a() {
  asm(""
      :
      :
      : "a0", "a1", "a2", "a3", "a4", "a5", "a6", "a7", "t0", "t1", "t2", "t3",
        "t4", "t5", "t6", "ra");
}

Error message:
during RTL pass: ira
/scratch1/kitoc/riscv-gnu-workspace/riscv-gnu-toolchain-trunk/riscv-gcc/gcc/testsuite/gcc.target/riscv/pr95252-2.c:
In function 'a':
/scratch1/kitoc/riscv-gnu-workspace/riscv-gnu-toolchain-trunk/riscv-gcc/gcc/testsuite/gcc.target/riscv/pr95252-2.c:10:1:
internal compiler error: in riscv_gpr_save_operation_p, at
config/riscv/riscv.c:5219
   10 | }
      | ^
0x1662745 riscv_gpr_save_operation_p(rtx_def*)
       
../../../../riscv-gnu-toolchain-trunk/riscv-gcc/gcc/config/riscv/riscv.c:5219
0x1a6829d gpr_save_operation_1
       
../../../../riscv-gnu-toolchain-trunk/riscv-gcc/gcc/config/riscv/predicates.md:213
0x1a682cf gpr_save_operation(rtx_def*, machine_mode)
       
../../../../riscv-gnu-toolchain-trunk/riscv-gcc/gcc/config/riscv/predicates.md:220
0x1a7e441 recog(rtx_def*, rtx_insn*, int*)
       
../../../../riscv-gnu-toolchain-trunk/riscv-gcc/gcc/config/riscv/riscv.md:2499
0x10cdd2c recog_memoized
        ../../../../riscv-gnu-toolchain-trunk/riscv-gcc/gcc/recog.h:167
0x10d6dd8 elimination_costs_in_insn
        ../../../../riscv-gnu-toolchain-trunk/riscv-gcc/gcc/reload1.c:3525
0x10d1aa1 calculate_elim_costs_all_insns()
        ../../../../riscv-gnu-toolchain-trunk/riscv-gcc/gcc/reload1.c:1604
0xeba7fc ira_costs()
        ../../../../riscv-gnu-toolchain-trunk/riscv-gcc/gcc/ira-costs.c:2293
0xeb0b2d ira_build()
        ../../../../riscv-gnu-toolchain-trunk/riscv-gcc/gcc/ira-build.c:3432
0xea6877 ira
        ../../../../riscv-gnu-toolchain-trunk/riscv-gcc/gcc/ira.c:5353
0xea70f4 execute
        ../../../../riscv-gnu-toolchain-trunk/riscv-gcc/gcc/ira.c:5666
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

             reply	other threads:[~2020-06-15 14:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-15 14:23 kito.cheng at gmail dot com [this message]
2020-06-15 14:27 ` [Bug target/95683] RISC-V: " kito at gcc dot gnu.org
2020-06-16  2:15 ` cvs-commit at gcc dot gnu.org
2020-06-19  5:49 ` kito at gcc dot gnu.org
2020-07-09  7:25 ` cvs-commit 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-95683-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).