the variable and option name changed.

Test is updated to show what this patch changes.

In D64972#1593826, @reames wrote:

I'm not quite sure this is the right macro approach.

The comment near the code your modifying makes me thing the whole reasoning behind disabling future peeling and unrolling after the first peel may be flawed. It doesn't make sense to "use up" profiling information. Assuming we correctly updated our profiling when doing the transform, the resulting profile for the loop should indicate that it's cold and thus not profitable to further peel/unroll. If that's not happening, maybe there's another issue in play? (I wonder if your other profile bug fix may help here?)

p.s. I'm opened to being convinced that this is a practical answer, even if not an ideal one. Just make the argument. :)

Please, take a look.

Hi Philip, Thank you for review. I'll update a patch.

Abandon in a favor of https://reviews.llvm.org/D64235

Thanks to @davezarzycki who fixed it in
commit 12400b97838d78386920cbda3c9dadb9f8727ce3
Author: David Zarzycki <dave@znu.io>
Date: Mon Jul 15 14:12:35 2019 +0000

I decided to avoid using public API with predicate due to it will require introducing template function in template class and effectively moving implementation to LoopInfo.h

Make getUniqueExitBlocksHelper more general with using filter predicate.
Unit test is added.

In D64553#1580189, @lebedev.ri wrote:

May be good to have a test.

Handled Philip's comments.

Abandon in favor of https://reviews.llvm.org/D64309

rebase + changes according to review.

Rebase

Hi Florian, I will land this change with comment update because I do not understand what exactly comment needs to be fixed.
Feel free to update this review with details what wrong in comment you see and I will land it as follow-up patch.