public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/99706] New: [11 Regression] ICE: maximum number of generated reload insns per insn achieved (90)
Date: Mon, 22 Mar 2021 09:16:48 +0000	[thread overview]
Message-ID: <bug-99706-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99706
           Summary: [11 Regression] ICE: maximum number of generated
                    reload insns per insn achieved (90)
           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: asolokha at gmx dot com
  Target Milestone: ---
            Target: aarch64-linux-gnu

gcc-11.0.1-alpha20210321 snapshot (g:fc24ea2374259d401a46ce3526688b7e79d4cc13)
ICEs when compiling the following testcase w/ -O2 -ftree-loop-vectorize
-fno-tree-pta --param scev-max-expr-size=5:

int kk;

void
ii (int BUFSIZE)
{
  char buf[BUFSIZE], *ptr = buf;
  int i;

  for (i = 0; i < BUFSIZE; i++)
    *ptr++ = kk = 0;
}

% aarch64-linux-gnu-gcc-11.0.1 -O2 -ftree-loop-vectorize -fno-tree-pta --param
scev-max-expr-size=5 -c oeplxogh.c
during RTL pass: reload
oeplxogh.c: In function 'ii':
oeplxogh.c:11:1: internal compiler error: maximum number of generated reload
insns per insn achieved (90)
   11 | }
      | ^
0xd42ab0 lra_constraints(bool)
       
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210321/work/gcc-11-20210321/gcc/lra-constraints.c:5091
0xd2b3e5 lra(_IO_FILE*)
       
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210321/work/gcc-11-20210321/gcc/lra.c:2336
0xce15c4 do_reload
       
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210321/work/gcc-11-20210321/gcc/ira.c:5834
0xce15c4 execute
       
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-11.0.1_alpha20210321/work/gcc-11-20210321/gcc/ira.c:6020

I believe it is different from PR97141.

             reply	other threads:[~2021-03-22  9:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-22  9:16 asolokha at gmx dot com [this message]
2021-03-22  9:23 ` [Bug target/99706] " pinskia at gcc dot gnu.org
2021-03-22  9:33 ` pinskia at gcc dot gnu.org
2021-03-22  9:34 ` asolokha at gmx dot com
2021-03-22 10:16 ` rguenth at gcc dot gnu.org
2021-03-22 19:35 ` jakub at gcc dot gnu.org
2021-03-22 20:04 ` [Bug target/99706] [10/11 " pinskia at gcc dot gnu.org
2021-03-23 10:36 ` [Bug target/99706] [9/10/11 " jakub at gcc dot gnu.org
2021-03-23 11:43 ` jakub at gcc dot gnu.org
2021-03-23 13:45 ` jakub at gcc dot gnu.org
2021-06-01  8:19 ` [Bug target/99706] [9/10/11/12 " rguenth at gcc dot gnu.org
2022-05-27  9:44 ` [Bug target/99706] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:44 ` jakub at gcc dot gnu.org
2022-10-19  4:02 ` asolokha at gmx dot com
2023-07-07 10:39 ` [Bug target/99706] [11/12/13/14 " rguenth at gcc dot gnu.org
2024-03-11  2:52 ` [Bug target/99706] [11 " law 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-99706-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).