[Bug tree-optimization/44794] pre- and post-loops should not be unrolled.

[Bug tree-optimization/44794] pre- and post-loops should not be unrolled.

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44794

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|unassigned at gcc dot gnu.org      |rguenth at gcc dot gnu.org
   Last reconfirmed|                            |2023-03-09
             Status|UNCONFIRMED                 |ASSIGNED
     Ever confirmed|0                           |1

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
On trunk we end up with a vectorized loop with unrolled vectorized epilogue and
scalar iteration and with a scalar loop copy used for n == 1 and the case
when 'a' and 'b' alias, so this loop covers all possible 'n'.  Prefetching then
(rightfully) prefetches both of these which makes four out of them.

What can be improved is the upper bound on the iteration for the epilog loop as
created by tree_unroll_loop.  That results in the RTL unroller seeing

-  upper bound: 2147483646
-  likely upper bound: 2147483646
+  upper bound: 14
+  likely upper bound: 14
   realistic bound: -1
 ;; Unable to prove that the loop iterates constant times
+;; Not unrolling loop, doesn't roll

...

-  upper bound: 536870910
-  likely upper bound: 536870910
+  upper bound: 2
+  likely upper bound: 2
   realistic bound: -1
 ;; Unable to prove that the loop iterates constant times
+;; Not unrolling loop, doesn't roll

and thus only unrolling the main loops again.  The prefetching unrolling
should have been enough of course - I suppose the RTL unroller could detect
prefetch instructions and refrain from unrolling loops with prefetches
on the basis they are already tuned well (that could be also implemented
in the unroll control target hook).

I am testing a patch to improve the situation.

[Bug tree-optimization/44794] pre- and post-loops should not be unrolled.

[cvs-commit at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44794

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:a243ce2a52a6c62bc0d6be0b756a85dd9c1bceb7

commit r14-71-ga243ce2a52a6c62bc0d6be0b756a85dd9c1bceb7
Author: Richard Biener <rguenther@suse.de>
Date:   Thu Mar 9 09:02:07 2023 +0100

    tree-optimization/44794 - avoid excessive RTL unrolling on epilogues

    The following adjusts tree_[transform_and_]unroll_loop to set an
    upper bound on the number of iterations on the epilogue loop it
    creates.  For the testcase at hand which involves array prefetching
    this avoids applying RTL unrolling to them when -funroll-loops is
    specified.

    Other users of this API includes predictive commoning and
    unroll-and-jam.

            PR tree-optimization/44794
            * tree-ssa-loop-manip.cc (tree_transform_and_unroll_loop):
            If an epilogue loop is required set its iteration upper bound.

[Bug tree-optimization/44794] pre- and post-loops should not be unrolled.

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44794

--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
Heuristic to not unroll loops with prefetches is missing.  The aprefetch pass
could set ->unroll to 1 in the loop structure.

[Bug tree-optimization/44794] pre- and post-loops should not be unrolled.

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44794

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|rguenth at gcc dot gnu.org         |unassigned at gcc dot gnu.org
             Status|ASSIGNED                    |NEW

[Bug tree-optimization/44794] pre- and post-loops should not be unrolled.

[changpeng dot fang at amd dot com]

------- Comment #4 from changpeng dot fang at amd dot com  2010-07-15 01:50 -------
Created an attachment (id=21205)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21205&action=view)
Do not unroll pre and post loops

I did a quick test on polyhedron before and after applying the preliminary
patch. Tests are based on -O3 -fprefetch-loop-arrays -funroll-loops.

               timing (s)      |     size (B)
         before after   %deduc | before after   %deduc          
cacacita 14.35  10.88   24.18  | 90715  72843   19.7
gas_dyn  34.68  21.58   37.77  | 149608 100936  32.53
nf       33.91  19.32   43.03  | 139150 83054   40.31
protein  51.35  33.23   35.29  | 163672 122808  24.97
rnflow   60.9   43.28   28.93  | 268784 169152  37.07
test_fpu 52.61  30.35   42.31  | 234045 144285  38.35


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44794

[Bug tree-optimization/44794] pre- and post-loops should not be unrolled.

[changpeng dot fang at amd dot com]

------- Comment #3 from changpeng dot fang at amd dot com  2010-07-06 18:35 -------
Here is the impact of loop unrolling on the compilation time and code size
on polyhedron test_fpu.f90:

-O3 -ftree-vectorize -fno-prefetch-loop-arrays -fno-unroll-loops:
timing: 12.62s,  size: 67069  bytes
-O3 -ftree-vectorize -fprefetch-loop-arrays -funroll-loops:
timing: 51.77s,  size: 234045 bytes


I also did an experiment on prefetching that we don't unroll the pre- and
post-loop generated by the vectorizer:
-O3 -ftree-vectorize -fprefetch-loop-arrays:
timing: 29.32s   size: 92541 bytes
-O3 -ftree-vectorize -fprefetch-loop-arrays (don't unroll pre- postloops)
timing: 18.34s   size: 78909 bytes 
-O3 -ftree-vectorize -fno-prefetch-loop-arrays
timing: 12.62s,  size: 67069  bytes


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44794

[Bug tree-optimization/44794] pre- and post-loops should not be unrolled.

[changpeng dot fang at amd dot com]

------- Comment #2 from changpeng dot fang at amd dot com  2010-07-06 17:58 -------
We also need to handle the post loop of unrolling. Suppose the unroll_factor
is 16, then the post-loop should have up to 15 iterations.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44794

[Bug tree-optimization/44794] pre- and post-loops should not be unrolled.

[rguenth at gcc dot gnu dot org]

------- Comment #1 from rguenth at gcc dot gnu dot org  2010-07-03 10:48 -------
It would be interesting to know why/if number-of-iteration analysis fails
and if the code the vectorizer emits can be adjusted to fix that.


-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rguenth at gcc dot gnu dot
                   |                            |org, rakdver at gcc dot gnu
                   |                            |dot org
           Severity|major                       |enhancement
            Version|lno                         |4.6.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44794