Eric Christopher a05ddd4b3a In the new pass manager use PTO.LoopUnrolling to determine when and how ... we will unroll loops. Also comment a few occasions where we need to know whether or not we're forcing the unwinder or not. The default before and after this patch is for LoopUnroll to be enabled, and for it to use a cost model to determine whether to unroll the loop (`OnlyWhenForced = false`). Before this patch, disabling loop unroll would not run the LoopUnroll pass. After this patch, the LoopUnroll pass is being run, but it restricts unrolling to only the loops marked by a pragma (`OnlyWhenForced = true`). In addition, this patch disables the UnrollAndJam pass when disabling unrolling. Testcase is in clang because it's controlling how the loop optimizer is being set up and there's no other way to trigger the behavior. llvm-svn: 374838		2019-10-14 22:56:07 +00:00
..
CMakeLists.txt	[New PM][PassInstrumentation] IR printing support for New Pass Manager	2018-09-24 16:08:15 +00:00
LLVMBuild.txt	Update the file headers across all of the LLVM projects in the monorepo	2019-01-19 08:50:56 +00:00
PassBuilder.cpp	In the new pass manager use PTO.LoopUnrolling to determine when and how	2019-10-14 22:56:07 +00:00
PassPlugin.cpp	Update the file headers across all of the LLVM projects in the monorepo	2019-01-19 08:50:56 +00:00
PassRegistry.def	Reapply r374743 with a fix for the ocaml binding	2019-10-14 16:15:14 +00:00
StandardInstrumentations.cpp	Update the file headers across all of the LLVM projects in the monorepo	2019-01-19 08:50:56 +00:00