390c0e2f72
Deopt operands are generally intended to record information about a site in code with minimal perturbation of the surrounding code. Idiomatically, they also tend to appear down rare paths. Putting these together, we have an obvious case for extending CVP w/deopt operand constant folding. Arguably, we should be doing this for all operands on all instructions, but that's definitely a much larger and risky change. Differential Revision: https://reviews.llvm.org/D55678 llvm-svn: 351774 |
||
|---|---|---|
| .. | ||
| 2010-09-02-Trunc.ll | ||
| 2010-09-26-MergeConstantRange.ll | ||
| add.ll | ||
| alloca.ll | ||
| ashr.ll | ||
| basic.ll | ||
| conflict.ll | ||
| crash.ll | ||
| deopt.ll | ||
| guards.ll | ||
| icmp.ll | ||
| non-null.ll | ||
| overflows.ll | ||
| phi-common-val.ll | ||
| pointer.ll | ||
| pr35807.ll | ||
| range.ll | ||
| sdiv.ll | ||
| select.ll | ||
| srem.ll | ||
| udiv.ll | ||
| urem.ll | ||