[PATCH] D105432: [Analysis] Add simple cost model for strict (in-order) reductions
David Sherwood via Phabricator via llvm-commits
llvm-commits at lists.llvm.org
Mon Jul 19 04:01:58 PDT 2021
david-arm added inline comments.
================
Comment at: llvm/lib/Target/AArch64/AArch64TargetTransformInfo.h:138
+ /// upon the maximum possible value for vscale.
+ unsigned getScalarizationCostFactor(ElementCount VF) const {
+ if (!VF.isScalable())
----------------
dmgreen wrote:
> getScalarizationCostFactor implies that it will be scalarized by codegen, and sounds similar to the already present getScalarizationOverhead. What do you think about something like getMaxNumLanes, as that appears to be what it computes.
Sure I can do that. I named it this way because I imagined we'll want to tweak this in future to something less pessimistic, perhaps based on mid-point between min and max? However, getMaxNumElements or Lanes works for now!
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D105432/new/
https://reviews.llvm.org/D105432
More information about the llvm-commits
mailing list