public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "david_harris at hmc dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/109687] New: riscv64-unknown-elf-gcc internal error on embench when using bit manipulation extensions Date: Mon, 01 May 2023 19:16:31 +0000 [thread overview] Message-ID: <bug-109687-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109687 Bug ID: 109687 Summary: riscv64-unknown-elf-gcc internal error on embench when using bit manipulation extensions Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: david_harris at hmc dot edu Target Milestone: --- Created attachment 54965 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54965&action=edit -freport-bug output This bug occurs when march=rv32imac_zba_zbb_zbs but not when march=rv32imac riscv64-unknown-elf-gcc -c -fdata-sections -ffunction-sections -march=rv32imac_zba_zbb_zbs -mabi=ilp32 -Os -msave-restore -I/home/harris/cvw/addins/embench-iot/support -I/home/harris/cvw/addins/embench-iot/config/riscv32/boards/rv32wallyverilog -I/home/harris/cvw/addins/embench-iot/config/riscv32/chips/generic -I/home/harris/cvw/addins/embench-iot/config/riscv32 -DCPU_MHZ=1 -DWARMUP_HEAT=1 -o libminver.o /home/harris/cvw/addins/embench-iot/src/minver/libminver.c /home/harris/cvw/addins/embench-iot/src/minver/libminver.c: In function 'minver.part.0': /home/harris/cvw/addins/embench-iot/src/minver/libminver.c:211:1: error: unrecognizable insn: 211 | } | ^ (insn 435 0 0 (set (reg:SI 275) (const_int 2048 [0x800])) -1 (expr_list:REG_EQUAL (const_int 2048 [0x800]) (nil))) during RTL pass: reload /home/harris/cvw/addins/embench-iot/src/minver/libminver.c:211:1: internal compiler error: in extract_insn, at recog.cc:2791 0x619df0 _fatal_insn(char const*, rtx_def const*, char const*, int, char const*) /opt/riscv/riscv-gnu-toolchain/gcc/gcc/rtl-error.cc:108 0x619e12 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*) /opt/riscv/riscv-gnu-toolchain/gcc/gcc/rtl-error.cc:116 0x6192dc extract_insn(rtx_insn*) /opt/riscv/riscv-gnu-toolchain/gcc/gcc/recog.cc:2791 0x9fe384 ira_remove_insn_scratches(rtx_insn*, bool, _IO_FILE*, rtx_def* (*)(rtx_def*)) /opt/riscv/riscv-gnu-toolchain/gcc/gcc/ira.cc:5356 0xa39509 remove_insn_scratches /opt/riscv/riscv-gnu-toolchain/gcc/gcc/lra.cc:2091 0xa3ae47 lra_emit_move(rtx_def*, rtx_def*) /opt/riscv/riscv-gnu-toolchain/gcc/gcc/lra.cc:512 0xa4e49d curr_insn_transform /opt/riscv/riscv-gnu-toolchain/gcc/gcc/lra-constraints.cc:4608 0xa4fc54 lra_constraints(bool) /opt/riscv/riscv-gnu-toolchain/gcc/gcc/lra-constraints.cc:5203 0xa3d8d2 lra(_IO_FILE*) /opt/riscv/riscv-gnu-toolchain/gcc/gcc/lra.cc:2375 0x9f86d9 do_reload /opt/riscv/riscv-gnu-toolchain/gcc/gcc/ira.cc:5940 0x9f86d9 execute /opt/riscv/riscv-gnu-toolchain/gcc/gcc/ira.cc:6126 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 reply other threads:[~2023-05-01 19:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-01 19:16 david_harris at hmc dot edu [this message] 2023-05-01 19:17 ` [Bug c/109687] " david_harris at hmc dot edu 2023-05-01 19:20 ` [Bug target/109687] " pinskia 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-109687-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).