public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/109092] New: [13 Regression] ICE: RTL check: expected code 'reg', have 'subreg' in rhs_regno, at rtl.h:1932 when building libgcc on riscv64 Date: Fri, 10 Mar 2023 17:32:26 +0000 [thread overview] Message-ID: <bug-109092-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109092 Bug ID: 109092 Summary: [13 Regression] ICE: RTL check: expected code 'reg', have 'subreg' in rhs_regno, at rtl.h:1932 when building libgcc on riscv64 Product: gcc Version: 13.0 Status: UNCONFIRMED Keywords: build, ice-on-valid-code Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: zsojka at seznam dot cz Target Milestone: --- Host: x86_64-pc-linux-gnu Target: riscv64-unknown-linux-gnu $ cat testcase.c void foo(int i) {} $ /repo/build-gcc-trunk-riscv64/./gcc/cc1 -mabi=lp64d -march=rv64imafdc testcase.c -quiet during RTL pass: vregs testcase.c: In function 'foo': testcase.c:1:18: internal compiler error: RTL check: expected code 'reg', have 'subreg' in rhs_regno, at rtl.h:1932 1 | void foo(int i) {} | ^ 0x7a0e7d rtl_check_failed_code1(rtx_def const*, rtx_code, char const*, int, char const*) /repo/gcc-trunk/gcc/rtl.cc:916 0x93b82e rhs_regno(rtx_def const*) /repo/gcc-trunk/gcc/rtl.h:1932 0x958236 rhs_regno(rtx_def const*) /repo/gcc-trunk/gcc/config/riscv/pic.md:87 0x958236 recog_17 /repo/gcc-trunk/gcc/config/riscv/riscv.md:1750 0x1ac76aa recog_174 /repo/gcc-trunk/gcc/config/riscv/vector-iterators.md:326 0xb527dc recog_memoized(rtx_insn*) /repo/gcc-trunk/gcc/recog.h:273 0xfdff84 extract_insn(rtx_insn*) /repo/gcc-trunk/gcc/recog.cc:2789 0xd111ff instantiate_virtual_regs_in_insn /repo/gcc-trunk/gcc/function.cc:1611 0xd111ff instantiate_virtual_regs /repo/gcc-trunk/gcc/function.cc:1985 0xd111ff execute /repo/gcc-trunk/gcc/function.cc:2034 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. Currently build with RTL checking enabled for the riscv64-unknown-linux-gnu target fails.
next reply other threads:[~2023-03-10 17:32 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-10 17:32 zsojka at seznam dot cz [this message] 2023-03-10 17:37 ` [Bug target/109092] " pinskia at gcc dot gnu.org 2023-03-13 8:52 ` rguenth at gcc dot gnu.org 2023-03-13 10:03 ` ubizjak at gmail dot com 2023-03-13 17:01 ` jakub at gcc dot gnu.org 2023-03-14 18:12 ` law at gcc dot gnu.org 2023-03-14 18:30 ` ubizjak at gmail dot com 2023-03-15 1:53 ` juzhe.zhong at rivai dot ai 2023-03-17 9:50 ` cvs-commit at gcc dot gnu.org 2023-03-27 7:44 ` pinskia at gcc dot gnu.org 2024-01-22 12:55 ` 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-109092-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).