diff options
| author | Tim Renouf <tim.renouf@amd.com> | 2019-12-03 20:09:53 +0000 |
|---|---|---|
| committer | Tim Renouf <tim.renouf@amd.com> | 2019-12-13 12:49:06 +0000 |
| commit | fce1a6f5848d644d56ab72d5bac71aa8053f8f2e (patch) | |
| tree | e6fa9edf11dcc48635f41a6e5debbb1686ce9b50 /lldb/packages/Python/lldbsuite/test/python_api/value/main.c | |
| parent | baea913609f1f3ddbd6fc6faf593524921507628 (diff) | |
| download | bcm5719-llvm-fce1a6f5848d644d56ab72d5bac71aa8053f8f2e.tar.gz bcm5719-llvm-fce1a6f5848d644d56ab72d5bac71aa8053f8f2e.zip | |
Revert "AMDGPU: Try to commute sub of boolean ext"
This reverts commit 69fcfb7d3597e0cdb5554b4e672e9032b411b167.
As shown in the test I attached to this commit, the change I reverted
causes a problem with "zext(cc1) - zext(cc2)". It commuted
the operands to the sub and used different logic to select the addc/subc
instruction:
sub zext (setcc), x => addcarry 0, x, setcc
sub sext (setcc), x => subcarry 0, x, setcc
... but that is bogus. I believe it is not possible to fold those commuted
patterns into any form of addcarry or subcarry. It may have worked as
intended before "AMDGPU: Change boolean content type to 0 or 1" because
the setcc was considered to be -1 rather than 1.
Differential Revision: https://reviews.llvm.org/D70978
Change-Id: If2139421aa6c935cbd1d925af58fe4a4aa9e8f43
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/value/main.c')
0 files changed, 0 insertions, 0 deletions
