summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py
diff options
context:
space:
mode:
authorSanjay Patel <spatel@rotateright.com>2016-07-13 16:04:07 +0000
committerSanjay Patel <spatel@rotateright.com>2016-07-13 16:04:07 +0000
commit610a2f65253526b866c230132cde8595a7303376 (patch)
tree00688089ac1d51acba971477d790ada4d68338e9 /lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py
parent9dfe4e7c0552c5cb2d1218efde271617a69c3827 (diff)
downloadbcm5719-llvm-610a2f65253526b866c230132cde8595a7303376.tar.gz
bcm5719-llvm-610a2f65253526b866c230132cde8595a7303376.zip
[x86][SSE/AVX] optimize pcmp results better (PR28484)
We know that pcmp produces all-ones/all-zeros bitmasks, so we can use that behavior to avoid unnecessary constant loading. One could argue that load+and is actually a better solution for some CPUs (Intel big cores) because shifts don't have the same throughput potential as load+and on those cores, but that should be handled as a CPU-specific later transformation if it ever comes up. Removing the load is the more general x86 optimization. Note that the uneven usage of vpbroadcast in the test cases is filed as PR28505: https://llvm.org/bugs/show_bug.cgi?id=28505 Differential Revision: http://reviews.llvm.org/D22225 llvm-svn: 275276
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud