diff options
| author | Craig Topper <craig.topper@intel.com> | 2019-10-16 02:50:04 +0000 |
|---|---|---|
| committer | Craig Topper <craig.topper@intel.com> | 2019-10-16 02:50:04 +0000 |
| commit | 7b49e8ac359bc35f95af548fbed4b7afd625caab (patch) | |
| tree | 9b6b76d1c8ac0514d01300f0a9a5ab54163b7139 /lldb/packages/Python/lldbsuite/test/python_api/section | |
| parent | 8200dbbcae933e79682b0f50f344befd3890c882 (diff) | |
| download | bcm5719-llvm-7b49e8ac359bc35f95af548fbed4b7afd625caab.tar.gz bcm5719-llvm-7b49e8ac359bc35f95af548fbed4b7afd625caab.zip | |
[LegalizeTypes] Don't call PromoteTargetBoolean from SplitVecOp_VSETCC.
PromoteTargetBoolean calls getSetccResultType to get the return
type. But we were passing it the setcc result type rather than the
setcc input type. This causes an issue on X86 with avx512vl where
the setcc result type for vXf16 vectors is vXi16 while the
result type for vXi16 vectors is vXi1.
There's really no guarantee that getSetccResultType is the type
we need here. So now we just grab the extend type from
getExtendForContent and extend to the original result VT of the
node we're splitting.
llvm-svn: 374970
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/section')
0 files changed, 0 insertions, 0 deletions
