This is an archive of the discontinued LLVM Phabricator instance.

[LoopUnrolling] Peel loops with invariant backedge Phi input
ClosedPublic

Authored by mkazantsev on Feb 20 2017, 1:59 AM.

Details

Summary

If a loop contains a Phi node which has an invariant input from back
edge, it is profitable to peel such loops (rather than unroll them) to
use the advantage that this Phi is always invariant starting from 2nd
iteration. After the 1st iteration is peeled, other optimizations can
potentially simplify calculations with this invariant.

Diff Detail

Repository
rL LLVM

Event Timeline

mkazantsev created this revision.Feb 20 2017, 1:59 AM
anna edited edge metadata.Feb 21 2017, 9:41 AM

Hi Max,

I'm not very sure about the change in priority of the loop peeling. There can be performance repercussions for that change alone, and might be better to get another opinion on the priority change.
Could you perhaps have this change as a strict improvement for loop peeling in itself?

lib/Transforms/Scalar/LoopUnrollPass.cpp
788 ↗(On Diff #89091)

Can this patch be separated into 2 parts, where the second part is this change to the priority?

lib/Transforms/Utils/LoopUnrollPeel.cpp
114 ↗(On Diff #89091)

There is a method for this getNumBackEdges. I think you can just reuse this and have a check against 1.

116 ↗(On Diff #89091)

can change this to for (auto *Pred: predecessors(Header))

mkazantsev added inline comments.Feb 21 2017, 9:13 PM
lib/Transforms/Scalar/LoopUnrollPass.cpp
788 ↗(On Diff #89091)

The problem here is that without this change, if UP.Partial is not set, line 803 prevents us from peeling (we return from method with false), and if UP.Partial is set, we may unroll the loop rather than peel it and have a worse result. So the test in this patch doesn't work without this re-prioritizing. I can split it into 2 patches, but priority change will be a parent and peeling change will depend on it.

mkazantsev marked 3 inline comments as done.

Addressed comments.

mkuper added a subscriber: mkuper.Feb 21 2017, 10:46 PM
mkuper added inline comments.
lib/Transforms/Utils/LoopUnrollPeel.cpp
113 ↗(On Diff #89321)

Can you just use L->getLoopLatch()? Or is that different from what you're looking for?

mkazantsev updated this revision to Diff 89344.Feb 22 2017, 2:58 AM
mkazantsev marked an inline comment as done.
reames added inline comments.Feb 24 2017, 5:30 PM
lib/Transforms/Utils/LoopUnrollPeel.cpp
118 ↗(On Diff #89344)

Out of curiosity, why the complexity about finding the backedge? Wouldn't *all* of the inputs to the phi be loop invariant in the case you're interested in?

mkazantsev added inline comments.Feb 26 2017, 9:07 PM
lib/Transforms/Utils/LoopUnrollPeel.cpp
118 ↗(On Diff #89344)

Off course, all inputs from preheaders will be invariant. Finding the backedge for header with n predecessors takes O(n) (it needs traversal over all predecessors with "contains" check in set that takes O(1). Acquiring its input also takes O(n) for every Phi, so total complexity being O(n*m) for m Phis.

If we just check all inputs for being invariants, it will also take O(n*m), but we will have positive results for loops with multiple back edges. The current implementation of peeling expects the loop to have 1 back edge, otherwise it will bail and we do unneded work with such loops.

mkazantsev updated this revision to Diff 89849.Feb 27 2017, 1:47 AM
mkazantsev retitled this revision from [LoopPeeling] Peel loops with invariant backedge Phi input to [LoopUnrolling] Peel loops with invariant backedge Phi input.
mkazantsev added a reviewer: mkuper.
mkazantsev updated this revision to Diff 90122.Feb 28 2017, 9:30 PM
mkuper edited edge metadata.Mar 1 2017, 2:25 PM

This generally LGTM, except for some nits. But please wait for @reames as well.

lib/Transforms/Utils/LoopUnrollPeel.cpp
83 ↗(On Diff #90122)

Why the parens around (Phi = ...)?

test/Transforms/LoopUnroll/peel-loop-not-forced.ll
1 ↗(On Diff #90122)

We generally prefer to test passes in isolation. Can you please make this a test for loop-unroll only?

reames edited edge metadata.Mar 1 2017, 6:59 PM

fine by me

mkazantsev updated this revision to Diff 90278.Mar 1 2017, 9:29 PM
mkazantsev marked 2 inline comments as done.
mkuper accepted this revision.Mar 2 2017, 10:07 AM
This revision is now accepted and ready to land.Mar 2 2017, 10:07 AM
This revision was automatically updated to reflect the committed changes.
efriedma added inline comments.
llvm/trunk/lib/Transforms/Utils/LoopUnrollPeel.cpp
95

Do we need to do some sort of threshold check here? At first glance, it looks like this will peel a loop of any size.