diff options
| author | Craig Topper <craig.topper@intel.com> | 2020-07-04 10:26:56 -0700 |
|---|---|---|
| committer | Craig Topper <craig.topper@intel.com> | 2020-07-04 10:26:56 -0700 |
| commit | e652c0f8f3e7c7a1b42edf22cfc5bbfd597fd164 (patch) | |
| tree | 8cec6f64b340305d5c24e9c28c916121a076c88f /clang/lib/Frontend/CompilerInvocation.cpp | |
| parent | b4eb415a996911132d1a9786a57846e75439e1f0 (diff) | |
| download | llvm-e652c0f8f3e7c7a1b42edf22cfc5bbfd597fd164.zip llvm-e652c0f8f3e7c7a1b42edf22cfc5bbfd597fd164.tar.gz llvm-e652c0f8f3e7c7a1b42edf22cfc5bbfd597fd164.tar.bz2 | |
[X86] Teach lowerShuffleAsBlend to use bit blend for v16i8/v32i8/v16i16 when avx512vl is enabled but not avx512bw.
Probably not super important since there are no real CPUs with
avx512vl and not avx512bw. But vpternlog should be better than
vblendvb.
I do wonder if we should use vpternlog even with BWI. We
currently use vblendmb or vpblendmw by putting the mask into a GPR
and moving it to a k-register. But I don't think we hoist the
GPR to k-register copy in machine LICM. Using VPTERNLOG would use
a constant pool load, but has the advantage that we're pretty good
at hoisting and rematerializing those.
Reviewed By: RKSimon
Differential Revision: https://reviews.llvm.org/D83156
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions