aboutsummaryrefslogtreecommitdiff
path: root/llvm/unittests/Support/CommandLineTest.cpp
diff options
context:
space:
mode:
authorFlorian Hahn <flo@fhahn.com>2023-12-08 18:30:30 +0000
committerGitHub <noreply@github.com>2023-12-08 18:30:30 +0000
commita5891fa4d2b76cf9dec96da9ded59fc4937d3342 (patch)
treec9e3b3899862a54d835fa317a47ac523058f2675 /llvm/unittests/Support/CommandLineTest.cpp
parent3810342e90c6206259817d98ac305db2be829285 (diff)
downloadllvm-a5891fa4d2b76cf9dec96da9ded59fc4937d3342.zip
llvm-a5891fa4d2b76cf9dec96da9ded59fc4937d3342.tar.gz
llvm-a5891fa4d2b76cf9dec96da9ded59fc4937d3342.tar.bz2
[VPlan] Initial modeling of VF * UF as VPValue. (#74761)
This patch starts initial modeling of VF * UF in VPlan. Initially, introduce a dedicated VFxUF VPValue, which is then populated during VPlan::prepareToExecute. Initially, the VF * UF applies only to the main vector loop region. Once we extend the scope of VPlan in the future, we may want to associate different VFxUFs with different vector loop regions (e.g. the epilogue vector loop) This allows explicitly parameterizing recipes that rely on the VF * UF, like the canonical induction increment. At the moment, this mainly helps to avoid generating some duplicated calls to vscale with scalable vectors. It should also allow using EVL as induction increments explicitly in D99750. Referring to VF * UF is also needed in other places that we plan to migrate to VPlan, like the minimum trip count check during skeleton creation. The first version creates the value for VF * UF directly in prepareToExecute to limit the scope of the patch. A follow-on patch will model VF * UF computation explicitly in VPlan using recipes. Moved from Phabricator (https://reviews.llvm.org/D157322)
Diffstat (limited to 'llvm/unittests/Support/CommandLineTest.cpp')
0 files changed, 0 insertions, 0 deletions