diff options
| author | David Sherwood <david.sherwood@arm.com> | 2021-09-22 10:54:05 +0100 |
|---|---|---|
| committer | David Sherwood <david.sherwood@arm.com> | 2021-10-21 09:33:50 +0100 |
| commit | 9448cdc90007611659ecbec4dca18a83f06bc4c3 (patch) | |
| tree | 2031c5fd73fef74613203c6c16de23cecc4f3292 /lldb/source/Plugins/OperatingSystem/Python/OperatingSystemPython.h | |
| parent | 92fb574c9f20aef56948c51f4921a92efbb72a5b (diff) | |
[SVE][Analysis] Tune the cost model according to the tune-cpu attribute
This patch introduces a new function:
AArch64Subtarget::getVScaleForTuning
that returns a value for vscale that can be used for tuning the cost
model when using scalable vectors. The VScaleForTuning option in
AArch64Subtarget is initialised according to the following rules:
1. If the user has specified the CPU to tune for we use that, else
2. If the target CPU was specified we use that, else
3. The tuning is set to "generic".
For CPUs of type "generic" I have assumed that vscale=2.
New tests added here:
Analysis/CostModel/AArch64/sve-gather.ll
Analysis/CostModel/AArch64/sve-scatter.ll
Transforms/LoopVectorize/AArch64/sve-strict-fadd-cost.ll
Differential Revision: https://reviews.llvm.org/D110259
Diffstat (limited to 'lldb/source/Plugins/OperatingSystem/Python/OperatingSystemPython.h')
0 files changed, 0 insertions, 0 deletions