Chandler Carruth 74564c24f8 [PM/Unswitch] Teach SimpleLoopUnswitch to do non-trivial unswitching, ... making it no longer even remotely simple. The pass will now be more of a "full loop unswitching" pass rather than anything substantively simpler than any other approach. I plan to rename it accordingly once the dust settles. The key ideas of the new loop unswitcher are carried over for non-trivial unswitching: 1) Fully unswitch a branch or switch instruction from inside of a loop to outside of it. 2) Update the CFG and IR. This avoids needing to "remember" the unswitched branches as well as avoiding excessively cloning and reliance on complex parts of simplify-cfg to cleanup the cfg. 3) Update the analyses (where we can) rather than just blowing them away or relying on something else updating them. Sadly, #3 is somewhat compromised here as the dominator tree updates were too complex for me to want to reason about. I will need to make another attempt to do this now that we have a nice dynamic update API for dominators. However, we do adhere to #3 w.r.t. LoopInfo. This approach also adds an important principls specific to non-trivial unswitching: not *all* of the loop will be duplicated when unswitching. This fact allows us to compute the cost in terms of how much *duplicate* code is inserted rather than just on raw size. Unswitching conditions which essentialy partition loops will work regardless of the total loop size. Some remaining issues that I will be addressing in subsequent commits: - Handling unstructured control flow. - Unswitching 'switch' cases instead of just branches. - Moving to the dynamic update API for dominators. Some high-level, interesting limitationsV that folks might want to push on as follow-ups but that I don't have any immediate plans around: - We could be much more clever about not cloning things that will be deleted. In fact, we should be able to delete *nothing* and do a minimal number of clones. - There are many more interesting selection criteria for which branch to unswitch that we might want to look at. One that I'm interested in particularly are a set of conditions which all exit the loop and which can be merged into a single unswitched test of them. Differential revision: https://reviews.llvm.org/D34200 llvm-svn: 318549		2017-11-17 19:58:36 +00:00
..
Coroutines	[coro] Make Spill a proper struct instead of deriving from pair.	2017-10-31 19:22:55 +00:00
Hello
InstCombine	[InstCombine] include 'sub' in the list of narrow-able binops	2017-11-16 14:40:51 +00:00
Instrumentation	[asan] Fix small X86_64 ShadowOffset for non-default shadow scale	2017-11-16 17:03:00 +00:00
IPO	Rename CountingFunctionInserter and use for both mcount and cygprofile calls, before and after inlining	2017-11-14 21:09:45 +00:00
ObjCARC	[Transforms] Fix some Clang-tidy modernize and Include What You Use warnings; other minor fixes (NFC).	2017-10-27 01:09:08 +00:00
Scalar	[PM/Unswitch] Teach SimpleLoopUnswitch to do non-trivial unswitching,	2017-11-17 19:58:36 +00:00
Utils	[PredicateInfo] Add comment about why we require stable sort	2017-11-17 00:43:24 +00:00
Vectorize	[SLP] Added more missed optimization remarks	2017-11-15 17:04:53 +00:00
CMakeLists.txt
LLVMBuild.txt