aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test/gdbclientutils.py
diff options
context:
space:
mode:
authorCraig Topper <craig.topper@sifive.com>2025-06-21 18:56:00 -0700
committerGitHub <noreply@github.com>2025-06-21 18:56:00 -0700
commitb7d0c9b9d8e2b5c5d6677e368e3cdaf438df294e (patch)
treecd0fc93b94ed3f2ae930c083e85cf073661d5da0 /lldb/packages/Python/lldbsuite/test/gdbclientutils.py
parentf280d3b705de7f94ef9756e3ef2842b415a7c038 (diff)
downloadllvm-b7d0c9b9d8e2b5c5d6677e368e3cdaf438df294e.zip
llvm-b7d0c9b9d8e2b5c5d6677e368e3cdaf438df294e.tar.gz
llvm-b7d0c9b9d8e2b5c5d6677e368e3cdaf438df294e.tar.bz2
[SelectionDAG][RISCV] Treat zext nneg as sext in PromoteIntOp_ZERO_EXTEND if the promoted input is sign extended. (#145120)
If the zext has the nneg flag and we can prove the promoted input is sign extended, we can avoid generating an AND that we might not be able to remove. RISC-V emits a lot of sext_inreg operations during i32->i64 promotion that makes this likely. I've restricted this to the case where the promoted type is the same as the result type so we don't need to create an additional extend. I've also restricted it to cases where the target has stated a preference for sext like i32->i64 on RV64. This is largely to avoid wasting time in computeNumSignBits until we have a test case that benefits.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/gdbclientutils.py')
0 files changed, 0 insertions, 0 deletions