[PATCH] D18670: LoopUnroll: some small fixes/tweaks to make it more useful for partial unrolling

[escha via llvm-commits]

escha added a comment.

FullUnrollMaxCount isn't used anywhere because it's a TTI option used by our out of tree target.

Count is a force-unroll option; it doesn't have anything to do with this, as far as I know.

MaxCount is what I would want, but it *specifically does not apply to full unrolling*, as specified in the documentation. I want to limit the number of iterations for a full unroll.

PartialThreshold, again, has nothing to do with full unrolls.

> I don't quiet understand the term 'put a cap on full unrolling'... If we can't unroll by compile-time-known tripcount, it becomes partial unrolling, right?


Yes, exactly. If the compile-time known tripcount is greater than FullUnrollMaxCount, it will fall back to partial unrolling instead, because it cannot do a full unroll.


Repository:
  rL LLVM

http://reviews.llvm.org/D18670