diff options
| author | Mauri Mustonen <mauri_mustonen@hotmail.com> | 2020-10-06 10:11:20 +0100 |
|---|---|---|
| committer | Florian Hahn <flo@fhahn.com> | 2020-10-06 10:11:58 +0100 |
| commit | cef0de5eb59dde6369645d37883f393354c99acd (patch) | |
| tree | 57af237ab61d6570e62c76717cfff355e6e434f2 /llvm/tools/llvm-objcopy/llvm-objcopy.cpp | |
| parent | f1ceaa200f9364ff6ca66a930872b19d99e5a339 (diff) | |
| download | llvm-cef0de5eb59dde6369645d37883f393354c99acd.zip llvm-cef0de5eb59dde6369645d37883f393354c99acd.tar.gz llvm-cef0de5eb59dde6369645d37883f393354c99acd.tar.bz2 | |
[VPlan] Add vplan native path vectorization test case for inner loop reduction
Regarding this bug I posted earlier: https://bugs.llvm.org/show_bug.cgi?id=47035
After reading through LLVM source code and getting familiar with VPlan I was able to vectorize the code using by enabling VPlan native path. After talking with @fhahn he suggested that I contribute this as a test case. So here it is. I tried to follow the available guides how to do this best I could. I modified IR code by hand to have more clear variable names instead of numbers.
One thing what I'd like to get input from someone is that is current CHECK lines sufficient enough to verify that the inner loop has been vectorized properly?
Reviewed By: fhahn
Differential Revision: https://reviews.llvm.org/D87564
Diffstat (limited to 'llvm/tools/llvm-objcopy/llvm-objcopy.cpp')
0 files changed, 0 insertions, 0 deletions