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/106815] New: [13 Regression] ICE: in riscv_excess_precision, at config/riscv/riscv.cc:5967 with -fexcess-precision=16 on any input Date: Fri, 02 Sep 2022 14:08:12 +0000 [thread overview] Message-ID: <bug-106815-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106815 Bug ID: 106815 Summary: [13 Regression] ICE: in riscv_excess_precision, at config/riscv/riscv.cc:5967 with -fexcess-precision=16 on any input 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 (empty testcase.c): $ echo '' > testcase.c $ riscv64-unknown-linux-gnu-gcc -fexcess-precision=16 testcase.c <built-in>: internal compiler error: in riscv_excess_precision, at config/riscv/riscv.cc:5967 0x7ada41 riscv_excess_precision /repo/gcc-trunk/gcc/config/riscv/riscv.cc:5967 0x7ada41 riscv_excess_precision /repo/gcc-trunk/gcc/config/riscv/riscv.cc:5956 0x94a206 c_ts18661_flt_eval_method /repo/gcc-trunk/gcc/c-family/c-common.cc:8939 0x98484a c_cpp_builtins(cpp_reader*) /repo/gcc-trunk/gcc/c-family/c-cppbuiltin.cc:1223 0x99fec7 c_finish_options /repo/gcc-trunk/gcc/c-family/c-opts.cc:1496 0x9a28b0 c_common_parse_file() /repo/gcc-trunk/gcc/c-family/c-opts.cc:1249 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-2374-20220902172530-gd72ca12b846-checking-yes-rtl-df-extra-riscv64/bin/../libexec/gcc/riscv64-unknown-linux-gnu/13.0.0/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-2374-20220902172530-gd72ca12b846-checking-yes-rtl-df-extra-riscv64 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 13.0.0 20220902 (experimental) (GCC)
next reply other threads:[~2022-09-02 14:08 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-02 14:08 zsojka at seznam dot cz [this message] 2022-09-03 1:31 ` [Bug target/106815] " palmer at gcc dot gnu.org 2022-09-05 10:00 ` rguenth at gcc dot gnu.org 2022-09-30 22:23 ` cvs-commit at gcc dot gnu.org 2022-10-19 6:11 ` rguenth 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-106815-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).