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 target/97269] New: [11 Regression] ICE in change_address_1, at emit-rtl.c:2275 since r11-3427-ge94797250b403d66cb3624a594e41faf0dd76617
Date: Fri, 02 Oct 2020 07:33:20 +0000	[thread overview]
Message-ID: <bug-97269-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97269

            Bug ID: 97269
           Summary: [11 Regression] ICE in change_address_1, at
                    emit-rtl.c:2275 since
                    r11-3427-ge94797250b403d66cb3624a594e41faf0dd76617
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
                CC: richard.sandiford at arm dot com
  Target Milestone: ---
              Host: x86_64-linux
            Target: arm-linux-gnueabihf

The following fails:

$ ./xgcc -B. /home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/20050309-1.c
-fstack-protector -mcpu=cortex-m7 -mpure-code -c
during RTL pass: mach
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/20050309-1.c: In function
‘test’:
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/20050309-1.c:41:1: internal
compiler error: in change_address_1, at emit-rtl.c:2275
   41 | }
      | ^
0xcc01cd change_address_1
        /home/marxin/Programming/gcc2/gcc/emit-rtl.c:2275
0xcc11be replace_equiv_address(rtx_def*, rtx_def*, bool)
        /home/marxin/Programming/gcc2/gcc/emit-rtl.c:2545
0xce498c validize_mem(rtx_def*)
        /home/marxin/Programming/gcc2/gcc/explow.c:531
0xd1273b emit_move_insn(rtx_def*, rtx_def*)
        /home/marxin/Programming/gcc2/gcc/expr.c:3931
0x1c3d582 gen_split_74(rtx_insn*, rtx_def**)
        /home/marxin/Programming/gcc2/gcc/config/arm/arm.md:9216
0x1e49f3b split_insns(rtx_def*, rtx_insn*)
        /home/marxin/Programming/gcc2/gcc/config/arm/arm.md:9192
0xcc3c4d try_split(rtx_def*, rtx_insn*, int)
        /home/marxin/Programming/gcc2/gcc/emit-rtl.c:3834
0x110b3c4 split_insn
        /home/marxin/Programming/gcc2/gcc/recog.c:2884
0x110b82d split_all_insns_noflow()
        /home/marxin/Programming/gcc2/gcc/recog.c:3046
0x16ca01b arm_reorg
        /home/marxin/Programming/gcc2/gcc/config/arm/arm.c:19143
0x11599c0 execute
        /home/marxin/Programming/gcc2/gcc/reorg.c:4028
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.

             reply	other threads:[~2020-10-02  7:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02  7:33 marxin at gcc dot gnu.org [this message]
2020-10-02  7:33 ` [Bug target/97269] " marxin at gcc dot gnu.org
2020-10-02 13:49 ` rguenth at gcc dot gnu.org
2020-10-12 11:46 ` rguenth at gcc dot gnu.org
2020-10-13  7:37 ` marxin at gcc dot gnu.org
2020-10-29 18:45 ` rsandifo at gcc dot gnu.org
2021-01-05 11:29 ` cvs-commit at gcc dot gnu.org
2021-01-05 11:31 ` rsandifo at gcc dot gnu.org
2021-03-29 11:47 ` rsandifo 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-97269-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).