public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/94440] [8/9/10/11 Regression] ICE in check_bool_attrs, at recog.c:2168 since r7-5324-gb8cab8a5492e9639
Date: Mon, 07 Dec 2020 13:28:06 +0000 [thread overview]
Message-ID: <bug-94440-4-ArDCqx0TF2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94440-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94440
--- Comment #13 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Jakub Jelinek from comment #10)
> I can't reproduce it anymore.
For r11-5820,
[hjl@gnu-clx-1 gcc]$ cat 1.c
int b;
double c, d;
void fn1() {
int i;
for (i = 0; i < b; i++)
c += i;
}
int __attribute__((optimize(1))) main() {
double a[0];
int i;
for (i = 0; i < 9; i++)
d += a[i];
}
[hjl@gnu-clx-1 gcc]$ ./xgcc -B./ -mfpmath=sse,387 -fexcess-precision=standard
-Ofast -fno-graphite --param=scev-max-expr-size=0 -m32 1.c
during RTL pass: reload
1.c: In function ??main??:
1.c:13:1: internal compiler error: in check_bool_attrs, at recog.c:2189
13 | }
| ^
0x6d21c1 check_bool_attrs(rtx_insn*)
../../src-master/gcc/recog.c:2189
0xc568e0 lra_update_insn_recog_data(rtx_insn*)
../../src-master/gcc/lra.c:1260
0xc7197b process_insn_for_elimination
../../src-master/gcc/lra-eliminations.c:1304
0xc7197b lra_eliminate(bool, bool)
../../src-master/gcc/lra-eliminations.c:1372
0xc578d9 lra(_IO_FILE*)
../../src-master/gcc/lra.c:2461
0xc13129 do_reload
../../src-master/gcc/ira.c:5802
0xc13129 execute
../../src-master/gcc/ira.c:5988
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.
[hjl@gnu-clx-1 gcc]$
next prev parent reply other threads:[~2020-12-07 13:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 12:47 [Bug rtl-optimization/94440] New: [8/9/10 " marxin at gcc dot gnu.org
2020-04-01 12:47 ` [Bug rtl-optimization/94440] " marxin at gcc dot gnu.org
2020-04-01 13:02 ` rguenth at gcc dot gnu.org
2020-04-01 13:23 ` ubizjak at gmail dot com
2020-04-01 13:38 ` jakub at gcc dot gnu.org
2020-04-01 14:05 ` jakub at gcc dot gnu.org
2020-04-01 14:07 ` ubizjak at gmail dot com
2020-04-01 14:09 ` marxin at gcc dot gnu.org
2020-04-01 14:21 ` jakub at gcc dot gnu.org
2020-04-18 16:28 ` law at redhat dot com
2020-07-30 15:42 ` [Bug rtl-optimization/94440] [8/9/10/11 " dcb314 at hotmail dot com
2020-10-09 7:12 ` dcb314 at hotmail dot com
2020-12-07 10:15 ` dcb314 at hotmail dot com
2020-12-07 12:38 ` jakub at gcc dot gnu.org
2020-12-07 12:56 ` dcb314 at hotmail dot com
2020-12-07 13:04 ` marxin at gcc dot gnu.org
2020-12-07 13:28 ` hjl.tools at gmail dot com [this message]
2020-12-07 14:06 ` jakub at gcc dot gnu.org
2020-12-07 16:48 ` jakub at gcc dot gnu.org
2020-12-08 14:44 ` cvs-commit at gcc dot gnu.org
2021-01-06 9:39 ` [Bug rtl-optimization/94440] [8/9/10 " cvs-commit at gcc dot gnu.org
2021-01-06 9:45 ` [Bug rtl-optimization/94440] [8/9 " jakub at gcc dot gnu.org
2021-04-27 11:38 ` jakub at gcc dot gnu.org
2021-07-28 7:04 ` [Bug rtl-optimization/94440] [9 " rguenth at gcc dot gnu.org
2022-01-05 19:18 ` ubizjak at gmail dot com
2022-04-21 7:47 ` rguenth at gcc dot gnu.org
2023-05-29 10:02 ` jakub 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-94440-4-ArDCqx0TF2@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).