Nikita Popov a17845f6c0 [LoopUnroll] Separate peeling from unrolling ... Loop peeling is currently performed as part of UnrollLoop(). Outside test scenarios, it is always performed with an unroll count of 1. This means that unrolling doesn't actually do anything apart from performing post-unroll simplification. When testing, it's currently possible to specify both an explicit peel count and an explicit unroll count. This doesn't perform any sensible operation and may result in miscompiles, see https://bugs.llvm.org/show_bug.cgi?id=45939. This patch moves peeling from UnrollLoop() into tryToUnrollLoop(), so that peeling does not also perform a susequent unroll. We only run the post-unroll simplifications. Specifying both an explicit peel count and unroll count is forbidden. In the future, we may want to support both (non-PGO) peeling a loop and unrolling it, but this needs to be done by first performing the peel and then recalculating unrolling heuristics on a now possibly analyzable loop. Differential Revision: https://reviews.llvm.org/D103362		2021-06-05 10:32:00 +02:00
..
llvm	[LoopUnroll] Separate peeling from unrolling	2021-06-05 10:32:00 +02:00
llvm-c	[ORC][C-bindings] Replace LLVMOrcJITTargetMachineBuilderDisposeTargetTriple.	2021-05-21 17:38:06 -07:00