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/97777] New: ICE: in df_refs_verify, at df-scan.c:3991 with -O -ffinite-math-only -fzero-call-used-regs=all
Date: Tue, 10 Nov 2020 11:06:50 +0000 [thread overview]
Message-ID: <bug-97777-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97777
Bug ID: 97777
Summary: ICE: in df_refs_verify, at df-scan.c:3991 with -O
-ffinite-math-only -fzero-call-used-regs=all
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords: 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: x86_64-pc-linux-gnu
Created attachment 49537
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49537&action=edit
reduced testcase
The compiler is configured with --enable-checking=yes,rtl,df,extra
Compiler output:
$ x86_64-pc-linux-gnu-gcc -O -ffinite-math-only -fzero-call-used-regs=all
testcase.c
during RTL pass: zero_call_used_regs
testcase.c: In function 'foo':
testcase.c:5:1: internal compiler error: in df_refs_verify, at df-scan.c:3991
5 | }
| ^
0x63bf73 df_refs_verify
/repo/gcc-trunk/gcc/df-scan.c:3991
0xbd44a6 df_insn_refs_verify
/repo/gcc-trunk/gcc/df-scan.c:4074
0xbd644c df_bb_verify
/repo/gcc-trunk/gcc/df-scan.c:4107
0xbd6807 df_scan_verify()
/repo/gcc-trunk/gcc/df-scan.c:4228
0xbc0757 df_verify()
/repo/gcc-trunk/gcc/df-core.c:1818
0xbc0757 df_analyze_1
/repo/gcc-trunk/gcc/df-core.c:1214
0xce77ec execute
/repo/gcc-trunk/gcc/function.c:6656
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
$ x86_64-pc-linux-gnu-gcc -v
Using built-in specs.
COLLECT_GCC=/repo/gcc-trunk/binary-latest/bin/x86_64-pc-linux-gnu-gcc
COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r11-4863-20201110102300-gfb54c3032b8-checking-yes-rtl-df-extra-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/11.0.0/lto-wrapper
Target: x86_64-pc-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 --build=x86_64-pc-linux-gnu
--host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu
--with-ld=/usr/bin/x86_64-pc-linux-gnu-ld
--with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r11-4863-20201110102300-gfb54c3032b8-checking-yes-rtl-df-extra-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 11.0.0 20201110 (experimental) (GCC)
next reply other threads:[~2020-11-10 11:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 11:06 zsojka at seznam dot cz [this message]
2020-11-12 18:14 ` [Bug rtl-optimization/97777] " ubizjak at gmail dot com
2020-11-12 20:52 ` qinzhao at gcc dot gnu.org
2020-11-12 22:17 ` qinzhao at gcc dot gnu.org
2020-11-16 16:37 ` qinzhao at gcc dot gnu.org
2020-11-16 21:13 ` qinzhao at gcc dot gnu.org
2020-12-02 22:48 ` cvs-commit at gcc dot gnu.org
2020-12-02 22:49 ` qinzhao 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-97777-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).