From: Richard Biener <richard.guenther@gmail.com>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Disable loop distribution for loops with estimated iterations 0
Date: Fri, 4 Aug 2023 10:19:19 +0200 [thread overview]
Message-ID: <CAFiYyc2Ms+11ueQPuSopGeU2CYO4GP6bEZfDSonz21ry6MhpAQ@mail.gmail.com> (raw)
In-Reply-To: <ZMylmGqvOtxn7pEf@kam.mff.cuni.cz>
On Fri, Aug 4, 2023 at 9:16 AM Jan Hubicka via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> Hi,
> this prevents useless loop distribiton produced in hmmer. With FDO we now
> correctly work out that the loop created for last iteraiton is not going to
> iterate however loop distribution still produces a verioned loop that has no
> chance to survive loop vectorizer since we only keep distributed loops
> when loop vectorization suceeds and it requires number of (header) iterations
> to exceed the vectorization factor.
>
> Bootstrapped/regtested x86_64-linux, OK?
OK.
But why does optimize_loop_for_speed_p () return true when the loop
isn't expected to iterate? Wouldn't that be a better place to fix this
and similar issues in other places then?
Thanks,
Richard.
> gcc/ChangeLog:
>
> * tree-loop-distribution.cc (loop_distribution::execute): Disable
> distribution for loops with estimated iterations 0.
>
> diff --git a/gcc/tree-loop-distribution.cc b/gcc/tree-loop-distribution.cc
> index cf7c197aaf7..8ff2108f284 100644
> --- a/gcc/tree-loop-distribution.cc
> +++ b/gcc/tree-loop-distribution.cc
> @@ -3871,10 +3871,20 @@ loop_distribution::execute (function *fun)
>
> bool destroy_p;
> int nb_generated_loops, nb_generated_calls;
> + bool only_patterns = !optimize_loop_for_speed_p (loop)
> + || !flag_tree_loop_distribution;
> + /* do not try to distribute loops that are not expected to iterate. */
> + if (!only_patterns)
> + {
> + HOST_WIDE_INT iterations = estimated_loop_iterations_int (loop);
> + if (iterations < 0)
> + iterations = likely_max_loop_iterations_int (loop);
> + if (!iterations)
> + only_patterns = true;
> + }
> nb_generated_loops
> = distribute_loop (loop, work_list, cd, &nb_generated_calls,
> - &destroy_p, (!optimize_loop_for_speed_p (loop)
> - || !flag_tree_loop_distribution));
> + &destroy_p, only_patterns);
> if (destroy_p)
> loops_to_be_destroyed.safe_push (loop);
>
next prev parent reply other threads:[~2023-08-04 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 7:15 Jan Hubicka
2023-08-04 8:19 ` Richard Biener [this message]
2023-08-04 8:58 ` Jan Hubicka
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=CAFiYyc2Ms+11ueQPuSopGeU2CYO4GP6bEZfDSonz21ry6MhpAQ@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
/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).