[ValueTracking] Remove dead code from an old experiment
authorPhilip Reames <listmail@philipreames.com>
Thu, 3 Mar 2016 19:44:06 +0000 (19:44 +0000)
committerPhilip Reames <listmail@philipreames.com>
Thu, 3 Mar 2016 19:44:06 +0000 (19:44 +0000)
commit146307eb52f1fa03cf04a81e218807173d6e08f9
tree92f30d5ae1832b9d56a8eb785290146133c949e2
parent9bba75084b7bde6a6215d616f664d3d2486f4871
[ValueTracking] Remove dead code from an old experiment

This experiment was originally about trying to use facts implied dominating conditions to infer more precise known bits.  While the compile time was found to be acceptable on several large code bases, we never found sufficiently profitable examples to justify turning on the code by default.  Given this, it's time to abandon the experiment.

Several folks have commented that they've found this useful for experimentation, but nothing has come of those experiments.  Given how easy the patch is to apply, there's no reason to leave the code in tree.

For anyone interested in further investigation in this area, I recommend finding the summary email I sent on one of the original review threads.  In particular, I now believe the use-list based approach is strictly worse than the dom-tree-walking approach.

llvm-svn: 262646
llvm/lib/Analysis/ValueTracking.cpp
llvm/test/Analysis/ValueTracking/dom-cond.ll [deleted file]
llvm/test/Analysis/ValueTracking/pr24866.ll [deleted file]
llvm/test/Transforms/InstCombine/dom-conditions.ll [deleted file]
llvm/test/Transforms/SeparateConstOffsetFromGEP/NVPTX/value-tracking-domtree.ll [deleted file]