| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
The AVX512 cases still need some work to correct recognise the PMOV truncation cases.
llvm-svn: 372514
|
|
|
|
|
|
|
|
| |
We are missing costs for a lot of truncation cases, I'm hoping to address all the 'zero cost' cases in trunc.ll
I thought this was a vector widening side effect, but even before this we had some interesting LV decisions (notably over indvars) being made due to these zero costs.
llvm-svn: 372498
|
|
|
|
|
|
| |
We were only testing costs for legal source vector element counts
llvm-svn: 350323
|
|
|
|
|
|
|
|
|
|
| |
we reasonably support. Add cost model tests for truncating to vXi1.
Our sext/zext cost modeling was somewhat incomplete. And had no coverage for the fact that avx512bw v32i16/v64i8 types return a scalarization cost.
Truncates are a whole different mess because isTruncateFree is returning true for vectors when it shouldn't and that's the fall back for anything not in the tables.
llvm-svn: 347719
|
|
|
|
| |
llvm-svn: 330433
|
|
|
|
|
|
| |
We're mostly testing with generic isa attributes, but PR36550 will require testing of specific target's scheduler models as well.
llvm-svn: 330056
|
|
|
|
|
|
| |
update_analyze_test_checks.py
llvm-svn: 329500
|
|
|
|
| |
llvm-svn: 314758
|
|
llvm-svn: 284938
|