Currently UP.PeelCount can be set by either TTI or -unroll-peel-count,
before computePeelCount is actually called. computePeelCount also checks
if the loop can be peeled and if we exit before calling it, the
PeelCount is set regardless whether the loop can be peeled or not.
If we exit before computePeelCount, we should set the PeelCount to 0.
Alternatively we could also just check if the loop is peel-able in
peelLoop(), but I think it is reasonable for the caller to ensure that
it is only called with peel-able loops. We could also call
computePeelCount, instead of setting it to zero, in case PeelCount != 0.
But that's probably worth doing as a follow-up.
Note that now it is not possible to combine peeling and unrolling in the
same step using LoopUnrollPass I think, hence the test changes.