summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py
diff options
context:
space:
mode:
authorAlexey Bataev <a.bataev@hotmail.com>2017-03-01 10:50:44 +0000
committerAlexey Bataev <a.bataev@hotmail.com>2017-03-01 10:50:44 +0000
commitdfec81107f2fbc804786b90523074194d70d8c30 (patch)
tree6f20771b2aa6dd785c52b75965849113abaa0bd5 /lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py
parenteab6cd474c478942949942d844da0ed51f31e394 (diff)
downloadbcm5719-llvm-dfec81107f2fbc804786b90523074194d70d8c30.tar.gz
bcm5719-llvm-dfec81107f2fbc804786b90523074194d70d8c30.zip
[SLP] Fix for PR32038: extra add of PHI node when it is not required.
Summary: If horizontal reduction tree starts from the binary operation that is used in PHI node, but this PHI is not used in horizontal reduction, we may end up with extra addition of this PHI node after vectorization. Here is an example: ``` %phi = phi i32 [ %tmp, %end], ... ... %tmp = add i32 %tmp1, %tmp2 end: ``` after vectorization we always have something like: ``` %phi = phi i32 [ %tmp, %end], ... ... %red = extractelement <8 x 32> %vec.red, 0 %tmp = add i32 %red, %phi end: ``` even if `%phi` is not used in reduction tree. Patch considers these PHI nodes as extra arguments and considers them in the final result iff they really used in reduction. Reviewers: mkuper, hfinkel, mzolotukhin Subscribers: llvm-commits Differential Revision: https://reviews.llvm.org/D30409 llvm-svn: 296606
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud