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

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2021-03-22
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
It is this RTL which is causing the issue:
(insn 31 27 29 4 (set (reg:V2DI 125 [ ivtmp.27 ])
        (subreg:V2DI (reg/f:DI 31 sp) 0)) 1163 {*aarch64_simd_movv2di}
     (expr_list:REG_DEAD (reg:TI 32 v0)
        (nil)))

Which was created while expanding (well sp is not there right away, it is done
later on):
  _42 = (sizetype) buf.1_10;
  _43 = _42 + 1;
  _44 = {_42, _43};

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

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-22  9:16 [Bug target/99706] New: " asolokha at gmx dot com
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 [this message]
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-TsfJZi9b9T@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).