public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/104637] [10/11 Regression] ICE: maximum number of LRA assignment passes is achieved (30) with -Og -fno-forward-propagate -mavx since r9-5221-gd8fcab689435a29d Date: Tue, 14 Jun 2022 15:50:40 +0000 [thread overview] Message-ID: <bug-104637-4-RqFYwCPr8p@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104637-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104637 --- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Vladimir Makarov <vmakarov@gcc.gnu.org>: https://gcc.gnu.org/g:688703569091edfd0400523d85cbb44d15aa61ea commit r10-10830-g688703569091edfd0400523d85cbb44d15aa61ea Author: Vladimir N. Makarov <vmakarov@redhat.com> Date: Mon Feb 28 16:43:50 2022 -0500 [PR104637] LRA: Split hard regs as many as possible on one subpass LRA hard reg split subpass is a small subpass used as the last resort for LRA when it can not assign a hard reg to a reload pseudo by other ways (e.g. by spilling non-reload pseudos). For simplicity the subpass works on one split base (as each split changes pseudo live range info). In this case it results in reaching maximal possible number of subpasses. The patch implements as many non-overlapping hard reg splits splits as possible on each subpass. gcc/ChangeLog: PR rtl-optimization/104637 * lra-assigns.c (lra_split_hard_reg_for): Split hard regs as many as possible on one subpass. gcc/testsuite/ChangeLog: PR rtl-optimization/104637 * gcc.target/i386/pr104637.c: New.
next prev parent reply other threads:[~2022-06-14 15:50 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-22 12:15 [Bug target/104637] New: ICE: maximum number of LRA assignment passes is achieved (30) with -Og -fno-forward-propagate -mavx zsojka at seznam dot cz 2022-02-24 15:17 ` [Bug target/104637] ICE: maximum number of LRA assignment passes is achieved (30) with -Og -fno-forward-propagate -mavx since r9-5221-gd8fcab689435a29d marxin at gcc dot gnu.org 2022-02-25 13:14 ` [Bug target/104637] [9/10/11/12 Regression] " jakub at gcc dot gnu.org 2022-02-25 13:25 ` jakub at gcc dot gnu.org 2022-02-25 16:57 ` vmakarov at gcc dot gnu.org 2022-02-28 21:45 ` cvs-commit at gcc dot gnu.org 2022-03-02 10:08 ` [Bug rtl-optimization/104637] " cvs-commit at gcc dot gnu.org 2022-03-02 14:00 ` vmakarov at gcc dot gnu.org 2022-03-15 8:29 ` [Bug rtl-optimization/104637] [9/10/11 " jakub at gcc dot gnu.org 2022-05-27 9:47 ` [Bug rtl-optimization/104637] [10/11 " rguenth at gcc dot gnu.org 2022-06-07 2:20 ` sam at gentoo dot org 2022-06-14 15:48 ` cvs-commit at gcc dot gnu.org 2022-06-14 15:48 ` cvs-commit at gcc dot gnu.org 2022-06-14 15:50 ` cvs-commit at gcc dot gnu.org [this message] 2022-06-14 15:50 ` cvs-commit at gcc dot gnu.org 2022-06-14 15:53 ` vmakarov at gcc dot gnu.org 2022-06-28 10:48 ` jakub at gcc dot gnu.org 2022-06-29 18:02 ` herrtimson at yahoo dot de 2022-06-29 19:01 ` ubizjak at gmail dot com 2022-06-29 19:37 ` 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-104637-4-RqFYwCPr8p@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).