diff options
| author | Philip Reames <preames@rivosinc.com> | 2023-05-03 07:30:22 -0700 |
|---|---|---|
| committer | Philip Reames <listmail@philipreames.com> | 2023-05-03 07:35:23 -0700 |
| commit | 9fc5af1b8466606c0f11f7035451fad8126c0dd6 (patch) | |
| tree | e3f4a476e072741c51807c1a3d1cba4e4897fad9 /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp | |
| parent | 9f0d725744aa2f36395fdccd85a2f21b960ff661 (diff) | |
[RISCV] Use vslide1down lowering for two element non-constant build_vectors
When the values are in GPRs, the vslide1down lowering is always better. We need to greatly improve the splat-and-mask cost model to handle constants in a meaningful way, so for now, limit this to non-constant vectors.
This does send the "partially constant" case down the vslide1down path. This could cause some regressions, though I don't see any in practice.
The cost modeling for the general case is annoyingly tricky. We have a great amount of inconsistency around immediate operands, and as a result, the exact constant and exact lowering choice matters a lot. I'm hoping that we get a "good enough" result without modeling this exactly, but we may need to do something analogous to getIntMatCost (i.e. a search w/costing).
Differential Revision: https://reviews.llvm.org/D149667
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPython.cpp')
0 files changed, 0 insertions, 0 deletions
