aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Target/WebAssembly/Utils/WebAssemblyUtilities.cpp
diff options
context:
space:
mode:
authorPhilip Reames <listmail@philipreames.com>2021-05-26 11:16:11 -0700
committerPhilip Reames <listmail@philipreames.com>2021-05-26 11:18:25 -0700
commit9306bb638ff2b13fb8472b5b035e658c1dcbd74c (patch)
treedf1e5eba5e0ee1453d46b8711a46cba767da6a91 /llvm/lib/Target/WebAssembly/Utils/WebAssemblyUtilities.cpp
parente5eff533f7611967ae1ead99846d06597dcb8ee2 (diff)
downloadllvm-9306bb638ff2b13fb8472b5b035e658c1dcbd74c.zip
llvm-9306bb638ff2b13fb8472b5b035e658c1dcbd74c.tar.gz
llvm-9306bb638ff2b13fb8472b5b035e658c1dcbd74c.tar.bz2
[SCEV] Generalize getSmallConstantTripCount(L) for multiple exit loops
This came up in review for another patch, see https://reviews.llvm.org/D102982#2782407 for full context. I've reviewed the callers to make sure they can handle multiple exit loops w/non-zero returns. There's two cases in target cost models where results might change (Hexagon and PowerPC), but the results looked legal and reasonable. If a target maintainer wishes to back out the effect of the costing change, they should explicitly check for multiple exit loops and handle them as desired. Differential Revision: https://reviews.llvm.org/D103182
Diffstat (limited to 'llvm/lib/Target/WebAssembly/Utils/WebAssemblyUtilities.cpp')
0 files changed, 0 insertions, 0 deletions