public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/100782] [11 Regression] sh4 ICEs on -O2 -fPIE -fstack-protector: internal compiler error: in curr_insn_transform, at lra-constraints.c:4132 Date: Tue, 06 Jul 2021 21:29:32 +0000 [thread overview] Message-ID: <bug-100782-4-1kFC1ujW8u@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100782-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100782 --- Comment #4 from Sergei Trofimovich <slyfox at gcc dot gnu.org> --- Bisected down to r11-4577 commit 44fbc9c6e02ca5b8f98f25b514ed7588e7ba733d Author: Vladimir N. Makarov <vmakarov@redhat.com> Date: Fri Oct 30 15:05:22 2020 -0400 Take insn scratch RA requirements into account in IRA. The patch changes insn scratches which require registers for all insn alternatives (in other words w/o X constraint in scratch constraint string). This is done before IRA staring its work. LRA still continue to change the rest scratches (with X constraint and in insn created during IRA) into pseudos. As before the patch at the end of LRA work, spilled scratch pseudos (for which X constraint was chosen) changed into scratches back.
next prev parent reply other threads:[~2021-07-06 21:29 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-26 21:38 [Bug target/100782] New: " slyfox at gcc dot gnu.org 2021-05-28 10:32 ` [Bug target/100782] " rguenth at gcc dot gnu.org 2021-06-21 22:25 ` slyfox at gcc dot gnu.org 2021-07-06 6:52 ` rguenth at gcc dot gnu.org 2021-07-06 7:34 ` slyfox at gcc dot gnu.org 2021-07-06 21:29 ` slyfox at gcc dot gnu.org [this message] 2021-07-28 7:07 ` rguenth at gcc dot gnu.org 2021-08-09 6:51 ` slyfox at gcc dot gnu.org 2022-04-21 7:49 ` rguenth at gcc dot gnu.org 2023-05-29 10:05 ` [Bug target/100782] [11 Regression] sh4 ICEs on -O2 -fPIE -fstack-protector: internal compiler error: in curr_insn_transform, at lra-constraints.c jakub 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-100782-4-1kFC1ujW8u@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: linkBe 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).