public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/111971] [12/13/14 regression] ICE: maximum number of generated reload insns per insn achieved (90) since r12-6803-g85419ac59724b7
Date: Thu, 26 Oct 2023 17:28:29 +0000 [thread overview]
Message-ID: <bug-111971-4-aMreFVwRia@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111971-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111971
--- Comment #6 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #4)
> But r1 is the argument register.
It is even worse, r1 is a stack pointer. Still the compilation should not
finish by LRA failure.
I've just started to work on this problem. I hope a patch fixing this will be
committed on this week or at the beginning of the next week.
next prev parent reply other threads:[~2023-10-26 17:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 2:35 [Bug rtl-optimization/111971] New: ICE: maximum number of generated reload insns per insn achieved (90) guojiufu at gcc dot gnu.org
2023-10-25 2:36 ` [Bug rtl-optimization/111971] " guojiufu at gcc dot gnu.org
2023-10-25 2:37 ` guojiufu at gcc dot gnu.org
2023-10-25 2:50 ` pinskia at gcc dot gnu.org
2023-10-25 2:51 ` pinskia at gcc dot gnu.org
2023-10-25 8:28 ` guojiufu at gcc dot gnu.org
2023-10-26 17:28 ` vmakarov at gcc dot gnu.org [this message]
2023-10-27 12:31 ` [Bug rtl-optimization/111971] [12/13/14 regression] ICE: maximum number of generated reload insns per insn achieved (90) since r12-6803-g85419ac59724b7 rguenth at gcc dot gnu.org
2023-10-31 15:45 ` cvs-commit at gcc dot gnu.org
2023-11-22 8:32 ` guojiufu 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-111971-4-aMreFVwRia@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).