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 tree-optimization/103409] [12 Regression] 18% SPEC2017 WRF compile-time regression with -O2 -flto since r12-5228-gb7a23949b0dcc4205fcc2be6b84b91441faa384d Date: Wed, 01 Dec 2021 16:12:31 +0000 [thread overview] Message-ID: <bug-103409-4-9TZXdpyI4Z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103409-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103409 --- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Aldy Hernandez <aldyh@gcc.gnu.org>: https://gcc.gnu.org/g:54ebec35abec09a24b47b997172622ca0d8e2318 commit r12-5694-g54ebec35abec09a24b47b997172622ca0d8e2318 Author: Aldy Hernandez <aldyh@redhat.com> Date: Mon Nov 29 14:49:59 2021 +0100 path solver: Use only one ssa_global_cache. We're using a temporary range cache while computing ranges for PHIs to make sure the real cache doesn't get set until all PHIs are computed. With the ltrans beast in LTO mode this causes undue overhead. Since we already have a bitmap to indicate whether there's a cache entry, we can avoid the extra cache object by clearing it while PHIs are being calculated. gcc/ChangeLog: PR tree-optimization/103409 * gimple-range-path.cc (path_range_query::compute_ranges_in_phis): Do all the work with just one ssa_global_cache. * gimple-range-path.h: Remove m_tmp_phi_cache.
next prev parent reply other threads:[~2021-12-01 16:12 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-24 16:35 [Bug tree-optimization/103409] New: 18% WRF compile-time regression with -O2 -flto between g:1ae8edf5f73ca5c3 and g:1ae8edf5f73ca5c3 hubicka at gcc dot gnu.org 2021-11-25 1:06 ` [Bug tree-optimization/103409] " pinskia at gcc dot gnu.org 2021-11-25 1:18 ` [Bug tree-optimization/103409] 18% WRF compile-time regression with -O2 -flto between g:264f061997c0a534 and g:3e09331f6aeaf595 pinskia at gcc dot gnu.org 2021-11-25 8:32 ` [Bug tree-optimization/103409] [12 Regression] " hubicka at kam dot mff.cuni.cz 2021-11-25 8:58 ` hubicka at gcc dot gnu.org 2021-11-25 9:47 ` [Bug tree-optimization/103409] [12 Regression] 18% SPEC2017 " marxin at gcc dot gnu.org 2021-11-25 15:00 ` marxin at gcc dot gnu.org 2021-11-25 18:12 ` [Bug tree-optimization/103409] [12 Regression] 18% SPEC2017 WRF compile-time regression with -O2 -flto since r12-3903-g0288527f47cec669 marxin at gcc dot gnu.org 2021-11-25 22:25 ` hubicka at kam dot mff.cuni.cz 2021-11-26 12:22 ` [Bug tree-optimization/103409] [12 Regression] 18% SPEC2017 WRF compile-time regression with -O2 -flto since r12-5228-gb7a23949b0dcc4205fcc2be6b84b91441faa384d marxin at gcc dot gnu.org 2021-11-26 12:34 ` hubicka at gcc dot gnu.org 2021-11-29 14:22 ` aldyh at gcc dot gnu.org 2021-11-29 14:36 ` aldyh at gcc dot gnu.org 2021-12-01 16:12 ` cvs-commit at gcc dot gnu.org [this message] 2021-12-01 16:14 ` aldyh at gcc dot gnu.org 2021-12-01 20:49 ` hubicka at kam dot mff.cuni.cz 2021-12-03 11:25 ` aldyh at gcc dot gnu.org 2021-12-03 11:28 ` hubicka 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-103409-4-9TZXdpyI4Z@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).