From: Jeff Law <jeffreyalaw@gmail.com>
To: Aldy Hernandez <aldyh@redhat.com>, GCC patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Remove loop crossing restriction from the backward threader.
Date: Thu, 11 Nov 2021 10:35:24 -0700 [thread overview]
Message-ID: <be4a7d31-589c-5c72-dca8-10774c214252@gmail.com> (raw)
In-Reply-To: <20211111172432.893034-1-aldyh@redhat.com>
On 11/11/2021 10:24 AM, Aldy Hernandez wrote:
> We have much more thorough restrictions, that are shared between both
> threader implementations, in the registry. I've been meaning to
> remove the backward threader one, since it's only purpose was reducing
> the search space. Previously there was a small time penalty for its
> removal, but with the various patches in the past month, it looks like
> the removal is a wash performance wise.
>
> This catches 8 more jump threads in the backward threader in my suite.
> Presumably, because we disallowed all loop crossing, whereas the
> registry restrictions allow some crossing (if we exit the loop, etc).
>
> OK pending tests on x86-64 Linux?
>
> gcc/ChangeLog:
>
> * tree-ssa-threadbackward.c
> (back_threader_profitability::profitable_path_p): Remove loop
> crossing restriction.
OK
jeff
prev parent reply other threads:[~2021-11-11 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 17:24 Aldy Hernandez
2021-11-11 17:24 ` [PATCH] Make ranger optional in path_range_query Aldy Hernandez
2021-11-11 17:35 ` 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=be4a7d31-589c-5c72-dca8-10774c214252@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=aldyh@redhat.com \
--cc=gcc-patches@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: 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).