Description
mze --cycles claims to show T-state cycle count, but always reports 0 T-states regardless of program complexity.
Reproduction
# Create a simple test binary: LD A,2 → OUT ($FE),A → RET
printf '\x3E\x02\xD3\xFE\xC9' > /tmp/test.bin
mze /tmp/test.bin --cycles -t spectrum --load 0x8000 --timeout 1000 -v
Expected: Total execution: 28 T-states (7 + 11 + 10)
Actual: Total execution: 0 T-states
Context
We're writing a Z80 book ("Coding the Impossible") and want to use mze --cycles to validate T-state annotations in chapter examples. This would enable automated cycle count verification via make test-run.
Impact
Blocks automated T-state validation for the book's ~25 assembly examples.
Description
mze --cyclesclaims to show T-state cycle count, but always reports0 T-statesregardless of program complexity.Reproduction
Expected:
Total execution: 28 T-states(7 + 11 + 10)Actual:
Total execution: 0 T-statesContext
We're writing a Z80 book ("Coding the Impossible") and want to use
mze --cyclesto validate T-state annotations in chapter examples. This would enable automated cycle count verification viamake test-run.Impact
Blocks automated T-state validation for the book's ~25 assembly examples.