summaryrefslogtreecommitdiffstats
path: root/lldb/source/Core/ValueObjectMemory.cpp
diff options
context:
space:
mode:
authorCraig Topper <craig.topper@intel.com>2019-01-28 21:38:47 +0000
committerCraig Topper <craig.topper@intel.com>2019-01-28 21:38:47 +0000
commit390ac61b930e745c4a7130a20ede62aa2370ffc0 (patch)
tree57b133577101f5e63dc20e0ddd433d736c4642b1 /lldb/source/Core/ValueObjectMemory.cpp
parent61bc1d7ed56b6eb6ad89c3c623078de3b20f82e5 (diff)
downloadbcm5719-llvm-390ac61b930e745c4a7130a20ede62aa2370ffc0.tar.gz
bcm5719-llvm-390ac61b930e745c4a7130a20ede62aa2370ffc0.zip
Recommit r352255 "[SelectionDAG][X86] Don't use SEXTLOAD for promoting masked loads in the type legalizer"
This did not cause the buildbot failure it was previously reverted for. Original commit message: I'm not sure why we were using SEXTLOAD. EXTLOAD seems more appropriate since we don't care about the upper bits. This patch changes this and then modifies the X86 post legalization combine to emit a extending shuffle instead of a sign_extend_vector_inreg. Could maybe use an any_extend_vector_inre On AVX512 targets I think we might be able to use a masked vpmovzx and not have to expand this at all. llvm-svn: 352433
Diffstat (limited to 'lldb/source/Core/ValueObjectMemory.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud