public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: Richard Biener <rguenther@suse.de>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] tree-optimization/102943 - avoid (re-)computing dominance bitmap
Date: Thu, 10 Mar 2022 20:31:13 -0700	[thread overview]
Message-ID: <7e532d87-840e-c556-d71d-d3e8ced74a77@gmail.com> (raw)
In-Reply-To: <20220310115042.DAE0413FA3@imap2.suse-dmz.suse.de>



On 3/10/2022 4:50 AM, Richard Biener via Gcc-patches wrote:
> Currently back_propagate_equivalences tries to optimize dominance
> queries in a smart way but it fails to notice that when fast indexes
> are available the dominance query is fast (when called from DOM).
> It also re-computes the dominance bitmap for each equivalence recorded
> on an edge, which for FP are usually several.  Finally it fails to
> use the tree bitmap view for efficiency.  Overall this cuts 7
> seconds of compile-time from originally 77 in the slowest LTRANS
> unit when building 521.wrf_r.
>
> Bootstrap and regtest running on x86_64-unknown-linux-gnu.
>
> Richard.
>
> 2022-03-10  Richard Biener  <rguenther@suse.de>
>
> 	PR tree-optimization/102943
> 	* tree-ssa-dom.cc (back_propagate_equivalences): Only
> 	populate the dominance bitmap if fast queries are not
> 	available.  Use a tree view bitmap.
> 	(record_temporary_equivalences): Cache the dominance bitmap
> 	across all equivalences on the edge.
Anything that helps WRF build times is a win in my book.    IIRC the 
worst module in there takes something like 27 minutes to cross compile 
for our target.  Annoying as hell when you have to do it multiple times 
a day.

jeff


      reply	other threads:[~2022-03-11  3:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 11:50 Richard Biener
2022-03-11  3:31 ` Jeff Law [this message]

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=7e532d87-840e-c556-d71d-d3e8ced74a77@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rguenther@suse.de \
    /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: link
Be 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).