diff options
| author | Pavel Labath <pavel@labath.sk> | 2020-03-06 10:47:33 +0100 |
|---|---|---|
| committer | Pavel Labath <pavel@labath.sk> | 2020-03-06 11:05:07 +0100 |
| commit | aa73ee052fffb0d06c6b7d8caf0271652c07a80d (patch) | |
| tree | c76bec8a805f123cb3efce99938a397bd4ecc93a /lldb/packages/Python/lldbsuite/test/lldbtest.py | |
| parent | eaddbc238d5fcca19432939223c87e4011b66546 (diff) | |
| download | llvm-aa73ee052fffb0d06c6b7d8caf0271652c07a80d.zip llvm-aa73ee052fffb0d06c6b7d8caf0271652c07a80d.tar.gz llvm-aa73ee052fffb0d06c6b7d8caf0271652c07a80d.tar.bz2 | |
[lldb/test] Use inline assembly for instruction counting tests
We have a test which checks that instruction-step really steps one
instruction, but the way it checks this makes it very susceptible to
codegen changes. This rewrites the test inferior to use inline assembly,
which guarantees a known sequence of instructions that the test can
check. This does mean we have to write separate assembly for each
architecture, but that is no better than having architecture-specific
assertions, which the test was already starting to accumulate.
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lldbtest.py')
0 files changed, 0 insertions, 0 deletions