aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp
diff options
context:
space:
mode:
authorSanjay Patel <spatel@rotateright.com>2020-01-27 16:33:13 -0500
committerSanjay Patel <spatel@rotateright.com>2020-01-27 16:35:50 -0500
commit747242af8dd03916ab46a16c1e38e716550cb60b (patch)
tree30fd46ee3eca53fb4012e6f8d631ec1199f65940 /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp
parent74df89f67f17f1e95c249831ce2d9c9d9830e496 (diff)
downloadllvm-747242af8dd03916ab46a16c1e38e716550cb60b.zip
llvm-747242af8dd03916ab46a16c1e38e716550cb60b.tar.gz
llvm-747242af8dd03916ab46a16c1e38e716550cb60b.tar.bz2
[InstCombine] allow more narrowing of casted select
D47163 created a rule that we should not change the casted type of a select when we have matching types in its compare condition. That was intended to help vector codegen, but it also could create situations where we miss subsequent folds as shown in PR44545: https://bugs.llvm.org/show_bug.cgi?id=44545 By using shouldChangeType(), we can continue to get the vector folds (because we always return false for vector types). But we also solve the motivating bug because it's ok to narrow the scalar select in that example. Our canonicalization rules around select are a mess, but AFAICT, this will not induce any infinite looping from the reverse transform (but we'll need to watch for that possibility if committed). Side note: there's a similar use of shouldChangeType() for phi ops just below this diff, and the source and destination types appear to be reversed. Differential Revision: https://reviews.llvm.org/D72733
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp')
0 files changed, 0 insertions, 0 deletions