mirror of
https://github.com/esphome/esphome.git
synced 2026-09-17 18:18:43 +00:00
J. Nick Koston
942cb0733b
cleanup_() has a two-line fast path (check to_remove count, return !items_.empty()) with the slow path already out-of-line in cleanup_slow_path_(). Despite `inline` hint, GCC on Xtensa emits it as a separate function, adding unnecessary call overhead on every Scheduler::call() invocation even when there is nothing to clean up. Use ESPHOME_ALWAYS_INLINE to guarantee inlining. Verified on ESP8266: - cleanup_() symbol eliminated from binary - Scheduler::call() grows 4 bytes (inlined fast path) - Net savings: 23 bytes (27-byte out-of-line body removed) - Idle loop path: 1 out-of-line call instead of 2
