aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Support/ErrorHandling.cpp
diff options
context:
space:
mode:
authorBardia Mahjour <bmahjour@ca.ibm.com>2020-12-02 10:07:41 -0500
committerBardia Mahjour <bmahjour@ca.ibm.com>2020-12-02 10:09:56 -0500
commita7e2c2693997e26912787f231543221f8487e0e5 (patch)
treebdca120f8e41500f7627aa172fc4923dbecb772d /llvm/lib/Support/ErrorHandling.cpp
parent5045b831a3b9c364d6ef0f09c7a773ca451ae1cc (diff)
downloadllvm-a7e2c2693997e26912787f231543221f8487e0e5.zip
llvm-a7e2c2693997e26912787f231543221f8487e0e5.tar.gz
llvm-a7e2c2693997e26912787f231543221f8487e0e5.tar.bz2
[LV] Epilogue Vectorization with Optimal Control Flow (Recommit)
This is yet another attempt at providing support for epilogue vectorization following discussions raised in RFC http://llvm.1065342.n5.nabble.com/llvm-dev-Proposal-RFC-Epilog-loop-vectorization-tt106322.html#none and reviews D30247 and D88819. Similar to D88819, this patch achieve epilogue vectorization by executing a single vplan twice: once on the main loop and a second time on the epilogue loop (using a different VF). However it's able to handle more loops, and generates more optimal control flow for cases where the trip count is too small to execute any code in vector form. Reviewed By: SjoerdMeijer Differential Revision: https://reviews.llvm.org/D89566
Diffstat (limited to 'llvm/lib/Support/ErrorHandling.cpp')
0 files changed, 0 insertions, 0 deletions