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/113738] New: [14 Regression] ICE: in df_reg_chain_verify_unmarked, at df-scan.cc:4001 with -O2 -march=rv64gcv Date: Sat, 03 Feb 2024 10:21:40 +0000 [thread overview] Message-ID: <bug-113738-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113738 Bug ID: 113738 Summary: [14 Regression] ICE: in df_reg_chain_verify_unmarked, at df-scan.cc:4001 with -O2 -march=rv64gcv Product: gcc Version: 14.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 Created attachment 57305 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57305&action=edit reduced testcase (from gcc.dg/torture/pr45764.c) Compiler output: $ riscv64-unknown-linux-gnu-gcc -O2 -march=rv64gcv testcase.c during RTL pass: rtl_dce testcase.c: In function 'foo': testcase.c:7:1: internal compiler error: in df_reg_chain_verify_unmarked, at df-scan.cc:4001 7 | } | ^ 0xa138ee df_reg_chain_verify_unmarked /repo/gcc-trunk/gcc/df-scan.cc:4001 0xa15111 df_reg_chain_verify_unmarked /repo/gcc-trunk/gcc/df-scan.cc:4218 0xa15111 df_scan_verify() /repo/gcc-trunk/gcc/df-scan.cc:4264 0x11f06d1 df_verify() /repo/gcc-trunk/gcc/df-core.cc:1834 0x11f06d1 df_analyze_1 /repo/gcc-trunk/gcc/df-core.cc:1221 0x29de3d5 init_dce /repo/gcc-trunk/gcc/dce.cc:763 0x29e103d rest_of_handle_fast_dce /repo/gcc-trunk/gcc/dce.cc:1193 0x29e103d execute /repo/gcc-trunk/gcc/dce.cc:1290 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-r14-8771-20240203001826-g4b7d4d8a4af-checking-yes-rtl-df-extra-riscv64/bin/../libexec/gcc/riscv64-unknown-linux-gnu/14.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-r14-8771-20240203001826-g4b7d4d8a4af-checking-yes-rtl-df-extra-riscv64 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 14.0.1 20240203 (experimental) (GCC)
next reply other threads:[~2024-02-03 10:21 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-03 10:21 zsojka at seznam dot cz [this message] 2024-02-03 21:44 ` [Bug middle-end/113738] " pinskia at gcc dot gnu.org 2024-02-03 21:46 ` pinskia at gcc dot gnu.org 2024-03-06 19:57 ` law at gcc dot gnu.org 2024-03-06 20:22 ` law 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-113738-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).