public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/106586] New: riscv32 still broke with zba_zbb_zbc_zbs, ICE in do_SUBST in C++ code Date: Thu, 11 Aug 2022 17:40:59 +0000 [thread overview] Message-ID: <bug-106586-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106586 Bug ID: 106586 Summary: riscv32 still broke with zba_zbb_zbc_zbs, ICE in do_SUBST in C++ code Product: gcc Version: 12.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: pinskia at gcc dot gnu.org Target Milestone: --- Target: riscv /home/apinski/src/toolchain-riscv/riscv-build/./gcc/xgcc -shared-libgcc -B/home/apinski/src/toolchain-riscv/riscv-build/./gcc -nostdinc++ -L/home/apinski/src/toolchain-riscv/riscv-build/riscv32-marvelldpu-elf/libstdc++-v3/src -L/home/apinski/src/toolchain-riscv/riscv-build/riscv32-marvelldpu-elf/libstdc++-v3/src/.libs -L/home/apinski/src/toolchain-riscv/riscv-build/riscv32-marvelldpu-elf/libstdc++-v3/libsupc++/.libs -nostdinc -B/home/apinski/src/toolchain-riscv/riscv-build/riscv32-marvelldpu-elf/newlib/ -isystem /home/apinski/src/toolchain-riscv/riscv-build/riscv32-marvelldpu-elf/newlib/targ-include -isystem /home/apinski/src/toolchain-riscv/src/newlib/libc/include -B/home/apinski/src/toolchain-riscv/riscv-build/riscv32-marvelldpu-elf/libgloss/riscv32 -L/home/apinski/src/toolchain-riscv/riscv-build/riscv32-marvelldpu-elf/libgloss/libnosys -L/home/apinski/src/toolchain-riscv/src/libgloss/riscv32 -B/home/apinski/src/toolchain-riscv/riscv-build/../marvelldpu-tools/riscv32-marvelldpu-elf/bin/ -B/home/apinski/src/toolchain-riscv/riscv-build/../marvelldpu-tools/riscv32-marvelldpu-elf/lib/ -isystem /home/apinski/src/toolchain-riscv/riscv-build/../marvelldpu-tools/riscv32-marvelldpu-elf/include -isystem /home/apinski/src/toolchain-riscv/riscv-build/../marvelldpu-tools/riscv32-marvelldpu-elf/sys-include -L/home/apinski/src/toolchain-riscv/riscv-build/./ld -I/home/apinski/src/toolchain-riscv/src/libstdc++-v3/../libgcc -I/home/apinski/src/toolchain-riscv/riscv-build/riscv32-marvelldpu-elf/libstdc++-v3/include/riscv32-marvelldpu-elf -I/home/apinski/src/toolchain-riscv/riscv-build/riscv32-marvelldpu-elf/libstdc++-v3/include -I/home/apinski/src/toolchain-riscv/src/libstdc++-v3/libsupc++ -std=gnu++11 -fno-implicit-templates -Wall -Wextra -Wwrite-strings -Wcast-qual -Wabi=2 -fdiagnostics-show-location=once -ffunction-sections -fdata-sections -frandom-seed=cow-sstream-inst.lo -g -O2 -c ../../../../../src/libstdc++-v3/src/c++11/cow-sstream-inst.cc -o cow-sstream-inst.o -freport-bug during RTL pass: combine In file included from /home/apinski/src/toolchain-riscv/riscv-build/riscv32-marvelldpu-elf/libstdc++-v3/include/sstream:1218, from ../../../../../src/libstdc++-v3/src/c++11/sstream-inst.cc:34, from ../../../../../src/libstdc++-v3/src/c++11/cow-sstream-inst.cc:30: /home/apinski/src/toolchain-riscv/riscv-build/riscv32-marvelldpu-elf/libstdc++-v3/include/bits/sstream.tcc: In member function ‘void std::basic_stringbuf<_CharT, _Traits, _Alloc>::_M_pbump(char_type*, char_type*, off_type) [with _CharT = char; _Traits = std::char_traits<char>; _Alloc = std::allocator<char>]’: /home/apinski/src/toolchain-riscv/riscv-build/riscv32-marvelldpu-elf/libstdc++-v3/include/bits/sstream.tcc:286:5: internal compiler error: in do_SUBST, at combine.cc:701 286 | } | ^ 0x8e268f do_SUBST ../../src/gcc/combine.cc:700 0x1918186 subst ../../src/gcc/combine.cc:5579 0x191807a subst ../../src/gcc/combine.cc:5532 0x191807a subst ../../src/gcc/combine.cc:5532 0x191b4e7 try_combine ../../src/gcc/combine.cc:3299 0x1921c2b combine_instructions ../../src/gcc/combine.cc:1410 0x1921c2b rest_of_handle_combine ../../src/gcc/combine.cc:14978 0x1921c2b execute ../../src/gcc/combine.cc:15023 Please submit a full bug report, with preprocessed source. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions. Preprocessed source stored into /tmp/ccozqEz0.out file, please attach this to your bugreport. Will attach the preprocessed source in a few minutes.
next reply other threads:[~2022-08-11 17:40 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-11 17:40 pinskia at gcc dot gnu.org [this message] 2022-08-11 17:42 ` [Bug target/106586] " pinskia at gcc dot gnu.org 2022-08-11 17:46 ` pinskia at gcc dot gnu.org 2022-08-11 18:37 ` pinskia at gcc dot gnu.org 2022-08-11 18:47 ` pinskia at gcc dot gnu.org 2022-08-11 19:14 ` pinskia at gcc dot gnu.org 2022-08-11 22:16 ` pinskia at gcc dot gnu.org 2022-08-12 1:48 ` jiawei at iscas dot ac.cn 2022-08-12 1:55 ` pinskia at gcc dot gnu.org 2022-08-15 18:58 ` pinskia at gcc dot gnu.org 2022-08-15 21:37 ` pinskia at gcc dot gnu.org 2022-08-15 22:13 ` pinskia at gcc dot gnu.org 2022-08-15 22:20 ` pinskia at gcc dot gnu.org 2022-08-15 23:16 ` pinskia at gcc dot gnu.org 2022-08-24 19:20 ` cvs-commit at gcc dot gnu.org 2022-08-24 19:21 ` 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-106586-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).