aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test/configuration.py
diff options
context:
space:
mode:
authorJames Y Knight <jyknight@google.com>2022-09-19 16:17:18 -0400
committerJames Y Knight <jyknight@google.com>2022-10-26 14:06:08 -0400
commit26fdad031ca8baa2196a6c8c40c0a23c066e611e (patch)
treea6b1e5545f3ea464312aa6b708b30fc56fa40c06 /lldb/packages/Python/lldbsuite/test/configuration.py
parent23394cd81092b10fea92a9e3959354865082fad1 (diff)
downloadllvm-26fdad031ca8baa2196a6c8c40c0a23c066e611e.zip
llvm-26fdad031ca8baa2196a6c8c40c0a23c066e611e.tar.gz
llvm-26fdad031ca8baa2196a6c8c40c0a23c066e611e.tar.bz2
[MIPS] Fix useDeprecatedPositionallyEncodedOperands errors.
This is a follow-on to https://reviews.llvm.org/D134073. The number of MIPS16 changes here is a bit surprising. Many of the fields with mismatched names were NOT previously choosing the correct argument positionally, but instead doing something completely wrong (e.g. it would encode a register where an immediate was expected). But, machine-code generation for MIPS16 has never actually functioned. It's also fully untested, thus, the MIPS16 changes, despite changing behavior, breaks (and fixes) zero tests. This change does not fix MIPS16 output, but it ought to be at least incrementally less broken. Outside MIPS16, I believe the only functional change is to the 'ginvi' instruction: it was previously encoding garbage into a field which was specified to be '00'. Fortunately, it was covered by tests -- and the tests were testing the incorrect behavior. So, fixed. Differential Revision: https://reviews.llvm.org/D134220
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/configuration.py')
0 files changed, 0 insertions, 0 deletions