public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/99378] New: ICE in decompose_normal_address, at rtlanal.c:6710
Date: Thu, 04 Mar 2021 08:09:27 +0000 [thread overview]
Message-ID: <bug-99378-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99378
Bug ID: 99378
Summary: ICE in decompose_normal_address, at rtlanal.c:6710
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: marxin at gcc dot gnu.org
CC: vmakarov at gcc dot gnu.org
Target Milestone: ---
The following fails:
$ gcc /home/marxin/Programming/gcc/gcc/testsuite/gcc.target/i386/pr99123.c -O2
-c -funroll-all-loops
during RTL pass: reload
/home/marxin/Programming/gcc/gcc/testsuite/gcc.target/i386/pr99123.c: In
function ‘foo’:
/home/marxin/Programming/gcc/gcc/testsuite/gcc.target/i386/pr99123.c:51:1:
internal compiler error: in decompose_normal_address, at rtlanal.c:6710
51 | }
| ^
0x6ff9e3 decompose_normal_address
/home/marxin/Programming/gcc/gcc/rtlanal.c:6710
0x6ff9e3 decompose_address(address_info*, rtx_def**, machine_mode, unsigned
char, rtx_code)
/home/marxin/Programming/gcc/gcc/rtlanal.c:6787
0xcda45d process_address_1
/home/marxin/Programming/gcc/gcc/lra-constraints.c:3455
0xcdc618 process_address
/home/marxin/Programming/gcc/gcc/lra-constraints.c:3729
0xcdc618 curr_insn_transform
/home/marxin/Programming/gcc/gcc/lra-constraints.c:4044
0xce208e lra_constraints(bool)
/home/marxin/Programming/gcc/gcc/lra-constraints.c:5133
0xccdd0f lra(_IO_FILE*)
/home/marxin/Programming/gcc/gcc/lra.c:2336
0xc856e4 do_reload
/home/marxin/Programming/gcc/gcc/ira.c:5827
0xc856e4 execute
/home/marxin/Programming/gcc/gcc/ira.c:6013
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.
next reply other threads:[~2021-03-04 8:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 8:09 marxin at gcc dot gnu.org [this message]
2021-03-04 9:39 ` [Bug target/99378] [8/9/10/11 Regression] " jakub at gcc dot gnu.org
2021-03-04 16:53 ` vmakarov at gcc dot gnu.org
2021-03-05 16:44 ` cvs-commit at gcc dot gnu.org
2021-03-07 14:41 ` asolokha at gmx dot com
2021-03-08 16:33 ` [Bug target/99378] [8/9/10 " jakub at gcc dot gnu.org
2021-05-14 9:54 ` [Bug target/99378] [9/10 " jakub at gcc dot gnu.org
2021-06-01 8:19 ` rguenth at gcc dot gnu.org
2022-05-27 9:44 ` [Bug target/99378] [10 " rguenth at gcc dot gnu.org
2022-06-28 10:43 ` jakub at gcc dot gnu.org
2023-07-07 9:30 ` 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-99378-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).