From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Speedup DF dataflow solver
Date: Wed, 15 Feb 2023 11:33:42 +0100 [thread overview]
Message-ID: <Y+y1BjmP0M6mXayP@tucnak> (raw)
In-Reply-To: <20230214142154.09F8D13A21@imap2.suse-dmz.suse.de>
On Tue, Feb 14, 2023 at 03:21:53PM +0100, Richard Biener wrote:
> The following makes sure to process blocks that follow the current
> block in the iteration order in the same iteration and only postpone
> blocks that would be visited earlier to the next iteration.
>
> For the all.i testcase in PR26854 at -O2 this shaves off 50% of
> the time to solve the DF RD problem, other problems also improve
> but not as drastically.
>
> Bootstrapped on x86_64-unknown-linux-gnu, testing in progress.
>
> OK for trunk?
>
> Thanks,
> Richard.
>
> PR middle-end/26854
> * df-core.cc (df_worklist_propagate_forward): Put later
> blocks on worklist and only earlier blocks on pending.
> (df_worklist_propagate_backward): Likewise.
> (df_worklist_dataflow_doublequeue): Change the iteration
> to process new blocks in the same iteration if that
> maintains the iteration order.
LGTM.
Jakub
prev parent reply other threads:[~2023-02-15 10:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 14:21 Richard Biener
2023-02-15 10:33 ` Jakub Jelinek [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=Y+y1BjmP0M6mXayP@tucnak \
--to=jakub@redhat.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).