summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/process/main.cpp
diff options
context:
space:
mode:
authorAmaury Sechet <deadalnix@gmail.com>2018-01-29 20:54:33 +0000
committerAmaury Sechet <deadalnix@gmail.com>2018-01-29 20:54:33 +0000
commit015184b79ea85a12ba80f49442302361cb2706a8 (patch)
treee0c4a400756c035ec2d51a69893fcca232661db8 /lldb/packages/Python/lldbsuite/test/python_api/process/main.cpp
parent1cc575666f3c2a26d73a380d2ec0d6bfc0c8cd20 (diff)
downloadbcm5719-llvm-015184b79ea85a12ba80f49442302361cb2706a8.tar.gz
bcm5719-llvm-015184b79ea85a12ba80f49442302361cb2706a8.zip
[X86] Avoid using high register trick for test instruction
Summary: It seems it's main effect is to create addition copies when values are inr register that do not support this trick, which increase register pressure and makes the code bigger. The main noteworthy regression I was able to observe was pattern of the type (setcc (trunc (and X, C)), 0) where C is such as it would benefit from the hi register trick. To prevent this, a new pattern is added to materialize such pattern using a 32 bits test. This has the added benefit of working with any constant that is materializable as a 32bits immediate, not just the ones that can leverage the high register trick, as demonstrated by the test case in test-shrink.ll using the constant 2049 . Reviewers: craig.topper, niravd, spatel, hfinkel Subscribers: llvm-commits Differential Revision: https://reviews.llvm.org/D42646 llvm-svn: 323690
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/process/main.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud