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] [10/11 Regression] ICE: maximum number of generated reload insns per insn achieved (90)
Date: Mon, 22 Mar 2021 20:04:29 +0000 [thread overview]
Message-ID: <bug-99706-4-jMymRcnEbg@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
----------------------------------------------------------------------------
Version|11.0 |10.1.0
Summary|[11 Regression] ICE: |[10/11 Regression] ICE:
|maximum number of generated |maximum number of generated
|reload insns per insn |reload insns per insn
|achieved (90) |achieved (90)
Known to work| |7.3.0, 7.4.0
Known to fail| |10.0, 11.0
Target Milestone|11.0 |10.3
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Here is a testcase which fails at -O1 (without any other options) and above:
int kk;
typedef unsigned long long v2di __attribute__((vector_size(16) ));
void f(v2di);
void
ii (int BUFSIZE)
{
char buf[BUFSIZE], *ptr = buf;
int i;
unsigned long t = (unsigned long)buf;
v2di tt = {t, t+1};
f(tt);
}
----- CUT ----
This worked in GCC 7.3.0 and 7.4.0 but fails with 10.1.0 and above. I don't
have 9.x to test on though.
next prev parent reply other threads:[~2021-03-22 20:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 9:16 [Bug target/99706] New: [11 " 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
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 ` pinskia at gcc dot gnu.org [this message]
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-jMymRcnEbg@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).