diff options
| author | Luke Lau <luke@igalia.com> | 2025-09-05 08:23:47 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-09-05 00:23:47 +0000 |
| commit | 4e5e65e55dc5a5ffc6e3db321df7f118e1c42d38 (patch) | |
| tree | d9fc9d1a5766db96fe0239dcb3de3ebaa457ee38 /llvm/lib/TargetParser | |
| parent | 53efe0a892199570aef9823cf0b1bc50bf4d480b (diff) | |
| download | llvm-4e5e65e55dc5a5ffc6e3db321df7f118e1c42d38.zip llvm-4e5e65e55dc5a5ffc6e3db321df7f118e1c42d38.tar.gz llvm-4e5e65e55dc5a5ffc6e3db321df7f118e1c42d38.tar.bz2 | |
[VPlan] Only compute reg pressure if considered. NFCI (#156923)
In #149056 VF pruning was changed so that it only pruned VFs that
stemmed from MaxBandwidth being enabled.
However we always compute register pressure regardless of whether or not
max bandwidth is permitted for any VFs (via
`MaxPermissibleVFWithoutMaxBW`).
This skips the computation if not needed and renames the method for
clarity.
The diff in reg-usage.ll is due to the scalable VPlan not actually
having any maxbandwidth VFs, so I've changed it to check the
fixed-length VF instead, which is affected by maxbandwidth.
Diffstat (limited to 'llvm/lib/TargetParser')
0 files changed, 0 insertions, 0 deletions