aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/MachineTraceMetrics.cpp
diff options
context:
space:
mode:
authorPhilip Reames <listmail@philipreames.com>2021-12-03 17:11:58 -0800
committerPhilip Reames <listmail@philipreames.com>2021-12-03 17:19:25 -0800
commit1a25d0bfbb6b587caa03bacd121b67086a774598 (patch)
tree262416e7791b3c2f5a9fb25d64eaa821aef83b5f /llvm/lib/CodeGen/MachineTraceMetrics.cpp
parent6db200736c51a61834fd2e192d8a5fd71e0874b4 (diff)
downloadllvm-1a25d0bfbb6b587caa03bacd121b67086a774598.zip
llvm-1a25d0bfbb6b587caa03bacd121b67086a774598.tar.gz
llvm-1a25d0bfbb6b587caa03bacd121b67086a774598.tar.bz2
[LICM] Remove profile driven restriction on hoisting
This reverts change 2c391a5/D87551. As noted in the llvm-dev thread "LICM as canonical form" sent earlier today, introducing this was a major design change made without sufficient cause. A profile driven LICM is not an unreasonable design, it simply is not what we have. Switching to such a model requires a lot more work than just this patch, and broad aggeement that is the right direction for the optimizer as a whole. Worth noting is that all the tests included in the reverted changed are probably handled if we allow running unconstrained LICM, and later run LoopSink. As such, we have no public examples which motivate a profit based hoisting approach.
Diffstat (limited to 'llvm/lib/CodeGen/MachineTraceMetrics.cpp')
0 files changed, 0 insertions, 0 deletions