Oh my. I&#x27;ve worked in those car test and simulation SW environments (and a cross compiler for a weird engine), 
and now I&#x27;m working on compilers and compiler optimizations in a different industry.<p>You cannot compare that at all.<p>With engine simulation and control you have real-time loops, with the biggest problem being the latency. You reduce latency by getting better HW, better sensors, shorter distances, a better SW driver architecture.
You don&#x27;t optimize by finding patterns or counting occurrences at all, esp. not at run-time. You always have to be prepared for the worst case.
Plus you always have HW + SW combined. Any major important SW feature is always doubled in HW for security. It&#x27;s a different world.<p>With compilers there&#x27;s no real-time trouble (GC&#x27;s, ha!), mostly no loops, no worry about HW, cables, sensors or drivers. It&#x27;s pure abstraction.
With JIT compilers it&#x27;s a bit different, mostly a tradeoff memory + optimization overhead vs speed. More measurements and dynamic decisions.
But jit optimization in engine control? Nah.
And there&#x27;s never a HW cross check. Signals, interrupts may arrive or get lost. The machine will not hard reset and reboot if a signal gets lost. 
It does so in a car or in space or other industrial control environments.