aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python
diff options
context:
space:
mode:
authorLuke Lau <luke@igalia.com>2024-10-30 23:36:46 +0200
committerGitHub <noreply@github.com>2024-10-31 05:36:46 +0800
commit14045de250ea126029d43ff8f2f68e9614c394bc (patch)
treeace200bd64d8798a4f5db3ff5eb1b745a2b92f07 /lldb/source/Plugins/ScriptInterpreter/Python
parent74d8f3952c4acf6d57948983d7c5b0d0a7763c28 (diff)
downloadllvm-14045de250ea126029d43ff8f2f68e9614c394bc.zip
llvm-14045de250ea126029d43ff8f2f68e9614c394bc.tar.gz
llvm-14045de250ea126029d43ff8f2f68e9614c394bc.tar.bz2
[RISCV] Account for factor in interleave memory op costs (#111511)
Currently we cost an interleaved memory op as if it were a load/store of the widened vector type, but this was undercosting in all cases when compared to the measured performance of todays hardware. On the x280 at NF=2 and spacemit-x60 at NF=2,3 and 4, a segmented load is carried out as a wide load and NF LMUL shuffle ops: https://github.com/preames/bp3-microarch#vlseg_lmul_x_sew_throughput All other NFs go through a slow path. On the spacemit-x60 this is proportional to VLMAX * NF, and on the x280 proportional to the number of segments. This patch increases the cost by implementing a wide load + NF LMUL shuffle op cost for the lowest common denominator NF=2, and then a slower cost proportional to VL for the other NFs. In a follow up patch we can add a tuning flag to use the faster cost model for NF=3 and 4 on the spacemit-x60. Note that the FIXME about illegal vectors seems to have been fixed in #100436
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python')
0 files changed, 0 insertions, 0 deletions