John Brawn 84b21835f1 [LoopUnroll] Keep the loop test only on the first iteration of max-or-zero loops ... When we have a loop with a known upper bound on the number of iterations, and furthermore know that either the number of iterations will be either exactly that upper bound or zero, then we can fully unroll up to that upper bound keeping only the first loop test to check for the zero iteration case. Most of the work here is in plumbing this 'max-or-zero' information from the part of scalar evolution where it's detected through to loop unrolling. I've also gone for the safe default of 'false' everywhere but howManyLessThans which could probably be improved. Differential Revision: https://reviews.llvm.org/D25682 llvm-svn: 284818		2016-10-21 11:08:48 +00:00
..
Coroutines	[coroutines] Store an address of destroy OR cleanup part in the coroutine frame.	2016-10-08 00:22:50 +00:00
Hello	Add auto-exporting of symbols from tools so that plugins work on Windows	2016-05-26 11:16:43 +00:00
IPO	Conditionally eliminate library calls where the result value is not used	2016-10-18 21:36:27 +00:00
InstCombine	[InstCombine] use m_APInt to allow sub with constant folds for splat vectors	2016-10-14 16:31:54 +00:00
Instrumentation	[asan] Simplify calculation of stack frame layout extraction calculation of stack description into separate function.	2016-10-18 23:29:52 +00:00
ObjCARC	Use StringRef in ARCRuntimeEntryPoints APIs (NFC)	2016-10-05 01:15:04 +00:00
Scalar	[LoopUnroll] Keep the loop test only on the first iteration of max-or-zero loops	2016-10-21 11:08:48 +00:00
Utils	[LoopUnroll] Keep the loop test only on the first iteration of max-or-zero loops	2016-10-21 11:08:48 +00:00
Vectorize	[LV] Avoid emitting trivially dead instructions	2016-10-19 19:22:02 +00:00
CMakeLists.txt	[coroutines] Part 3 of N: Adding Boilerplate for Coroutine Passes	2016-07-28 21:04:31 +00:00
LLVMBuild.txt	[coroutines] Part 3 of N: Adding Boilerplate for Coroutine Passes	2016-07-28 21:04:31 +00:00