mirror of
https://github.com/esphome/esphome.git
synced 2026-02-28 09:54:19 -07:00
25b979bbed
When the scheduler lock is already held, atomic loads of the remove flag don't need acquire ordering — the mutex provides all necessary synchronization guarantees. Add is_item_removed_locked_() helper that uses memory_order_relaxed and use it in all _locked_ call sites. This eliminates redundant memw barriers on Xtensa, saving 12 bytes in matches_item_locked_ (152 → 140 B) and reducing pipeline stalls in the scheduler hot path.
