For now, this is just a wrapper around RunCycles(n), but the two could diverge in the future. RunMillis(t) should always cause `t` milliseconds to elapse in the simulator, regardless of how many cycles that takes. Signed-off-by: Michael Richters <gedankenexperimenter@gmail.com>pull/946/head
parent
3a16fc95fb
commit
69fc1dc0e2
Loading…
Reference in new issue