summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/functionalities/conditional_break
diff options
context:
space:
mode:
authorSimon Pilgrim <llvm-dev@redking.me.uk>2018-06-08 10:29:00 +0000
committerSimon Pilgrim <llvm-dev@redking.me.uk>2018-06-08 10:29:00 +0000
commitad45efc445e9dcabf0fc3d42dba89910630da4e3 (patch)
tree36cfdfa45a7ecd8887dc80422e0cfaf4bfa984f3 /lldb/packages/Python/lldbsuite/test/functionalities/conditional_break
parent84e6ef00dc96cedda96959f3e03852d2336c7b8c (diff)
downloadbcm5719-llvm-ad45efc445e9dcabf0fc3d42dba89910630da4e3.tar.gz
bcm5719-llvm-ad45efc445e9dcabf0fc3d42dba89910630da4e3.zip
[X86][SSE] Consistently prefer lowering to PACKUS over PACKSS
We have some combines/lowerings that attempt to use PACKSS-then-PACKUS and others that use PACKUS-then-PACKSS. PACKUS is much easier to combine with if we know the upper bits are zero as ComputeKnownBits can easily see through BITCASTs etc. especially now that rL333995 and rL334007 have landed. It also effectively works at byte level which further simplifies shuffle combines. The only (minor) annoyances are that ComputeKnownBits can sometimes take longer as it doesn't fail as quickly as ComputeNumSignBits (but I'm not seeing any actual regressions in tests) and PACKUSDW only became available after SSE41 so we have more codegen diffs between targets. llvm-svn: 334276
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/functionalities/conditional_break')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud