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 target/109104] New: [13 Regression] ICE: in gen_reg_rtx, at emit-rtl.cc:1171 with -fzero-call-used-regs=all -march=rv64gv
Date: Sat, 11 Mar 2023 10:53:50 +0000	[thread overview]
Message-ID: <bug-109104-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 109104
           Summary: [13 Regression] ICE: in gen_reg_rtx, at
                    emit-rtl.cc:1171 with -fzero-call-used-regs=all
                    -march=rv64gv
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: target
          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

Compiler output:
$ cat testcase.c 
void foo(void) {}
$ riscv64-unknown-linux-gnu-gcc -fzero-call-used-regs=all -march=rv64gv
testcase.c 
during RTL pass: zero_call_used_regs
testcase.c: In function 'foo':
testcase.c:1:17: internal compiler error: in gen_reg_rtx, at emit-rtl.cc:1171
    1 | void foo(void) {}
      |                 ^
0x6f9f83 gen_reg_rtx(machine_mode)
        /repo/gcc-trunk/gcc/emit-rtl.cc:1171
0x14ca5d4 emit_vlmax_vsetvl
        /repo/gcc-trunk/gcc/config/riscv/riscv-v.cc:115
0x14ca5d4 emit_pred_op
        /repo/gcc-trunk/gcc/config/riscv/riscv-v.cc:189
0x14ca9e1 riscv_vector::emit_vlmax_op(unsigned int, rtx_def*, rtx_def*,
machine_mode)
        /repo/gcc-trunk/gcc/config/riscv/riscv-v.cc:207
0x14ca9e1 expand_const_vector
        /repo/gcc-trunk/gcc/config/riscv/riscv-v.cc:239
0x14ca9e1 riscv_vector::legitimize_move(rtx_def*, rtx_def*, machine_mode)
        /repo/gcc-trunk/gcc/config/riscv/riscv-v.cc:265
0x19c9500 gen_movvnx2qi(rtx_def*, rtx_def*)
        /repo/gcc-trunk/gcc/config/riscv/vector.md:563
0xcbe9f1 rtx_insn* insn_gen_fn::operator()<rtx_def*, rtx_def*>(rtx_def*,
rtx_def*) const
        /repo/gcc-trunk/gcc/recog.h:407
0xcbe9f1 emit_move_insn_1(rtx_def*, rtx_def*)
        /repo/gcc-trunk/gcc/expr.cc:4172
0xcbee1f emit_move_insn(rtx_def*, rtx_def*)
        /repo/gcc-trunk/gcc/expr.cc:4342
0x109b93b default_zero_call_used_regs(HARD_REG_SET)
        /repo/gcc-trunk/gcc/targhooks.cc:1094
0xd1e4aa gen_call_used_regs_seq
        /repo/gcc-trunk/gcc/function.cc:5950
0xd1e4aa execute
        /repo/gcc-trunk/gcc/function.cc:6744
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.

$ riscv64-unknown-linux-gnu-gcc -v
Using built-in specs.
COLLECT_GCC=/repo/gcc-trunk/binary-latest-riscv64/bin/riscv64-unknown-linux-gnu-gcc
COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r13-6502-20230306110826-gb83acefb040-checking-yes-rtl-df-extra-riscv64/bin/../libexec/gcc/riscv64-unknown-linux-gnu/13.0.1/lto-wrapper
Target: riscv64-unknown-linux-gnu
Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++
--enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra
--with-cloog --with-ppl --with-isl --with-isa-spec=2.2
--with-sysroot=/usr/riscv64-unknown-linux-gnu --build=x86_64-pc-linux-gnu
--host=x86_64-pc-linux-gnu --target=riscv64-unknown-linux-gnu
--with-ld=/usr/bin/riscv64-unknown-linux-gnu-ld
--with-as=/usr/bin/riscv64-unknown-linux-gnu-as --disable-multilib
--disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r13-6502-20230306110826-gb83acefb040-checking-yes-rtl-df-extra-riscv64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.0.1 20230306 (experimental) (GCC)

             reply	other threads:[~2023-03-11 10:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11 10:53 zsojka at seznam dot cz [this message]
2023-03-11 16:31 ` [Bug target/109104] " pinskia at gcc dot gnu.org
2023-03-14  8:43 ` roger at nextmovesoftware dot com
2023-03-14  8:49 ` juzhe.zhong at rivai dot ai
2023-03-30 12:06 ` marxin at gcc dot gnu.org
2023-03-30 13:41 ` kito at gcc dot gnu.org
2023-03-31 14:44 ` yanzhang.wang at intel dot com
2023-04-08 14:34 ` law at gcc dot gnu.org
2023-04-11 14:09 ` cvs-commit at gcc dot gnu.org
2023-04-17 13:28 ` [Bug target/109104] [13/14 " kito 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-109104-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).