Chandler Carruth 176c94be9c [PM] Introduce a devirtualization iteration layer for the new PM. ... This is an orthogonal and separated layer instead of being embedded inside the pass manager. While it adds a small amount of complexity, it is fairly minimal and the composability and control seems worth the cost. The logic for this ends up being nicely isolated and targeted. It should be easy to experiment with different iteration strategies wrapped around the CGSCC bottom-up walk using this kind of facility. The mechanism used to track devirtualization is the simplest one I came up with. I think it handles most of the cases the existing iteration machinery handles, but I haven't done a *very* in depth analysis. It does however match the basic intended semantics, and we can tweak or tune its exact behavior incrementally as necessary. One thing that we may want to revisit is freshly building the value handle set on each iteration. While I don't think this will be a significant cost (it is strictly fewer value handles but more churn of value handes than the old call graph), it is conceivable that we'll want a somewhat more clever tracking mechanism. My hope is to layer that on as a follow up patch with data supporting any implementation complexity it adds. This code also provides for a basic count heuristic: if the number of indirect calls decreases and the number of direct calls increases for a given function in the SCC, we assume devirtualization is responsible. This matches the heuristics currently used in the legacy pass manager. Differential Revision: https://reviews.llvm.org/D23114 llvm-svn: 290665		2016-12-28 11:07:33 +00:00
..
CMakeLists.txt	[CMake] NFC. Updating CMake dependency specifications	2016-11-17 04:36:50 +00:00
LLVMBuild.txt	Add missing dependency to LLVMPasses	2016-06-24 21:05:41 +00:00
PassBuilder.cpp	[PM] Introduce a devirtualization iteration layer for the new PM.	2016-12-28 11:07:33 +00:00
PassRegistry.def	[NewGVN] Add the pass to PassRegistry.def.	2016-12-22 16:35:02 +00:00