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/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:53:50 +0000 [thread overview] Message-ID: <bug-104637-4-R7eaUqaKtA@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 #14 from Vladimir Makarov <vmakarov at gcc dot gnu.org> --- I've just ported the two patches to gcc-10 and gcc-11 release branches. gcc-10 required additional work besides just cherry-picking. The patches were successfully bootstrapped and tested on x86-64.
next prev parent reply other threads:[~2022-06-14 15:53 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 2022-06-14 15:50 ` cvs-commit at gcc dot gnu.org 2022-06-14 15:53 ` vmakarov at gcc dot gnu.org [this message] 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-R7eaUqaKtA@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).