SuccessChanges

Summary

  1. QEMU logging: do not report jumps from tight loops otherwise, some loops would print a huge amount of jumps (unnecessary) these would slow down certain tests a lot, e.g. 5D3 callstack on fromutility
  2. QEMU logging: record direct jumps to function calls (many such calls in DIGIC 6)
  3. QEMU logging: log task switches before other items otherwise, consistency errors may appear - see test_callstack.py minor differences in VxWorks tests
  4. QEMU: ignore CBZ (on Thumb-2 code)
Changeset 13630:cd37857dafec by alex@thinkpad:
QEMU logging: do not report jumps from tight loops<br>otherwise, some loops would print a huge amount of jumps (unnecessary)<br>these would slow down certain tests a lot, e.g. 5D3 callstack on fromutility
The file was modifiedcontrib/qemu/eos/dbi/logging.c (diff)
Changeset 13629:1edb651b8549 by alex@thinkpad:
QEMU logging: record direct jumps to function calls (many such calls in DIGIC 6)
The file was modifiedcontrib/qemu/eos/dbi/logging.c (diff)
The file was modifiedcontrib/qemu/tests/test_callstack.py (diff)
Changeset 13628:8b90df898cfa by alex@thinkpad:
QEMU logging: log task switches before other items<br>otherwise, consistency errors may appear - see test_callstack.py<br>minor differences in VxWorks tests
The file was modifiedcontrib/qemu/eos/dbi/logging.c (diff)
The file was modifiedcontrib/qemu/tests/1000D/calls-fint.md5 (diff)
The file was modifiedcontrib/qemu/tests/400D/calls-fint.md5 (diff)
The file was modifiedcontrib/qemu/tests/40D/calls-fint.md5 (diff)
The file was modifiedcontrib/qemu/tests/450D/calls-fint.md5 (diff)
Changeset 13627:dea9a0918369 by alex@thinkpad:
QEMU: ignore CBZ (on Thumb-2 code)
The file was modifiedcontrib/qemu/eos/dbi/logging.c (diff)