public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/98782] [11 Regression] Bad interaction between IPA frequences and IRA resulting in spills due to changes in BB frequencies Date: Tue, 23 Feb 2021 12:06:37 +0000 [thread overview] Message-ID: <bug-98782-4-tBWBUx5rtX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98782-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98782 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |11.0
next prev parent reply other threads:[~2021-02-23 12:06 UTC|newest] Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-21 14:31 [Bug rtl-optimization/98782] New: IRA artificially creating spills due to " tnfchris at gcc dot gnu.org 2021-01-21 14:35 ` [Bug rtl-optimization/98782] " jgreenhalgh at gcc dot gnu.org 2021-01-22 10:12 ` fxue at os dot amperecomputing.com 2021-01-29 13:34 ` tnfchris at gcc dot gnu.org 2021-02-05 12:02 ` [Bug rtl-optimization/98782] [11 Regression] Bad interaction between IPA frequences and IRA resulting in spills due to changes in " tnfchris at gcc dot gnu.org 2021-02-23 2:11 ` jiangning.liu at amperecomputing dot com 2021-02-23 12:06 ` rguenth at gcc dot gnu.org [this message] 2021-02-26 12:32 ` rguenth at gcc dot gnu.org 2021-11-28 19:07 ` [Bug rtl-optimization/98782] [11/12 " hubicka at gcc dot gnu.org 2021-11-29 1:33 ` jiangning.liu at amperecomputing dot com 2021-11-29 6:59 ` tnfchris at gcc dot gnu.org 2021-12-03 11:44 ` hubicka at gcc dot gnu.org 2021-12-03 11:47 ` hubicka at gcc dot gnu.org 2021-12-07 11:19 ` tnfchris at gcc dot gnu.org 2021-12-07 11:21 ` tnfchris at gcc dot gnu.org 2021-12-07 11:21 ` tnfchris at gcc dot gnu.org 2021-12-07 19:44 ` rsandifo at gcc dot gnu.org 2021-12-07 23:52 ` tnfchris at gcc dot gnu.org 2021-12-08 9:33 ` rsandifo at gcc dot gnu.org 2021-12-08 14:31 ` tnfchris at gcc dot gnu.org 2021-12-08 15:02 ` rsandifo at gcc dot gnu.org 2021-12-09 19:56 ` pthaugen at gcc dot gnu.org 2021-12-09 20:12 ` hubicka at gcc dot gnu.org 2021-12-09 21:27 ` pthaugen at gcc dot gnu.org 2021-12-10 11:36 ` hubicka at gcc dot gnu.org 2021-12-14 14:38 ` tnfchris at gcc dot gnu.org 2021-12-14 14:40 ` hubicka at kam dot mff.cuni.cz 2021-12-14 14:48 ` tnfchris at gcc dot gnu.org 2021-12-14 14:58 ` hubicka at kam dot mff.cuni.cz 2021-12-14 15:07 ` tnfchris at gcc dot gnu.org 2021-12-14 15:08 ` tnfchris at gcc dot gnu.org 2021-12-14 18:16 ` jamborm at gcc dot gnu.org 2021-12-15 12:15 ` tnfchris at gcc dot gnu.org 2021-12-20 18:06 ` rsandifo at gcc dot gnu.org 2021-12-31 17:28 ` rsandifo at gcc dot gnu.org 2022-01-04 22:26 ` pthaugen at gcc dot gnu.org 2022-01-04 22:29 ` pthaugen at gcc dot gnu.org 2022-01-06 14:53 ` rsandifo at gcc dot gnu.org 2022-01-10 1:29 ` crazylht at gmail dot com 2022-01-11 10:14 ` Jan Hubicka 2022-01-10 14:47 ` cvs-commit at gcc dot gnu.org 2022-01-10 14:47 ` cvs-commit at gcc dot gnu.org 2022-01-10 14:47 ` cvs-commit at gcc dot gnu.org 2022-01-10 14:47 ` cvs-commit at gcc dot gnu.org 2022-01-10 14:52 ` [Bug rtl-optimization/98782] [11 " rsandifo at gcc dot gnu.org 2022-01-11 10:14 ` hubicka at kam dot mff.cuni.cz 2022-01-11 14:22 ` rsandifo 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-98782-4-tBWBUx5rtX@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).