diff options
| author | Simon Pilgrim <llvm-dev@redking.me.uk> | 2018-12-19 13:37:59 +0000 |
|---|---|---|
| committer | Simon Pilgrim <llvm-dev@redking.me.uk> | 2018-12-19 13:37:59 +0000 |
| commit | 6c95bea072a8999818c26da9fec9332cdf6d9bee (patch) | |
| tree | 0d9b8c508c4c1bd3bd4727e93f77119858180233 /lldb/packages/Python/lldbsuite/test/lang/cpp/std-function-step-into-callable/main.cpp | |
| parent | f7cf1a1a7353dc5c578dfc85eb963e61a4d406cd (diff) | |
| download | bcm5719-llvm-6c95bea072a8999818c26da9fec9332cdf6d9bee.tar.gz bcm5719-llvm-6c95bea072a8999818c26da9fec9332cdf6d9bee.zip | |
[TargetLowering] Fix propagation of undefs in zero extension ops (PR40091)
As described on PR40091, we have several places where zext (and zext_vector_inreg) fold an undef input into an undef output. For zero extensions this is incorrect as the output should guarantee to least have the new upper bits set to zero.
SimplifyDemandedVectorElts is the worst offender (and its the most likely to cause new undefs to appear) but DAGCombiner's tryToFoldExtendOfConstant has a similar issue.
Thanks to @dmgreen for catching this.
Differential Revision: https://reviews.llvm.org/D55883
llvm-svn: 349625
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lang/cpp/std-function-step-into-callable/main.cpp')
0 files changed, 0 insertions, 0 deletions
