summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/api
diff options
context:
space:
mode:
authorCraig Topper <craig.topper@intel.com>2018-11-19 22:04:12 +0000
committerCraig Topper <craig.topper@intel.com>2018-11-19 22:04:12 +0000
commitdbe34736345a280c3836ba86775f49da522783df (patch)
tree0e012a0778943786f60146c1b61637a21dfd7ef6 /lldb/packages/Python/lldbsuite/test/api
parent700b1ef54daff2b99cb52c56db682721ef1094c8 (diff)
downloadbcm5719-llvm-dbe34736345a280c3836ba86775f49da522783df.tar.gz
bcm5719-llvm-dbe34736345a280c3836ba86775f49da522783df.zip
[X86] Add test case to show missed opportunity to use a single pmuludq to implement a multiply when a zext lives in another basic block.
This can occur when one of the inputs to the multiply is loop invariant. Though my test cases just use two basic blocks with an unconditional jump which we won't merge until after isel in the codegen pipeline. For scalars, I believe SelectionDAGBuilder can add an AssertZExt to pass knowledge across basic blocks but its explicitly disabled for vectors. llvm-svn: 347266
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/api')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud