Files
LibretroAdmin e9819f388b input: the null driver says no key is down
The null input driver had no keys_down, so the frontend took the slow
fallback for it: every frame it asked for every hotkey and every
user's turbo and hold bind one at a time, since it could not know that
none of them can be pressed. With keys_down saying no key is down, the
hotkey pass and the poll skip those reads, as they do for the drivers
that give their keys.

Callgrind over the frontend harness's input-cost lane, which runs on
this driver: 40% fewer instructions in all, 83% in the hotkey pass and
50% in input_driver_poll. Every lane gives the same results.

The harness mocks that copy the null driver to answer keys through
input_state now clear keys_down, so they still test that kind of
driver.
2026-11-08 00:15:24 +01:00
..