public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/108705] [13 Regression] Unexpected CPU time usage with LTO in ranger propagation Date: Fri, 10 Feb 2023 14:56:04 +0000 [thread overview] Message-ID: <bug-108705-4-YnVWYXCM1T@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108705-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108705 --- Comment #8 from Andrew Macleod <amacleod at redhat dot com> --- This fix I just checked in for 108687 exhibited similar performance characteristics, also in the same pass.. Perhaps it will fix your problem.
next prev parent reply other threads:[~2023-02-10 14:56 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-08 0:00 [Bug tree-optimization/108705] New: " rimvydas.jas at gmail dot com 2023-02-08 0:03 ` [Bug tree-optimization/108705] [13 Regression] " pinskia at gcc dot gnu.org 2023-02-08 4:39 ` rimvydas.jas at gmail dot com 2023-02-09 13:36 ` rguenth at gcc dot gnu.org 2023-02-09 14:01 ` amacleod at redhat dot com 2023-02-09 15:31 ` rimvydas.jas at gmail dot com 2023-02-09 16:06 ` amacleod at redhat dot com 2023-02-09 20:51 ` rimvydas.jas at gmail dot com 2023-02-09 20:54 ` rimvydas.jas at gmail dot com 2023-02-10 14:56 ` amacleod at redhat dot com [this message] 2023-02-10 15:35 ` rimvydas.jas at gmail dot com 2023-02-10 22:03 ` rimvydas.jas at gmail dot com
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-108705-4-YnVWYXCM1T@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).