A few yeArs ago, in the pages of this magazine, Edward Lee argued that computing needs time. 23 This article focuses on the natural assumption that computing also takes time. We examine the problem of determining how much time. It is the problem of verifying the real-time behavior of safety-critical embedded systems. For such systems, for example, anti-lock brakes and airbags, punctual behavior is of utmost importance: If the controlling computations take too long, quality of service degrades or the systems fail completely-your braking distance is longer or your head hits the steering wheel, respectively.The basis for verifying the timeliness of system reactions is reliable information on the execution times of all computational tasks involved. It is the job of timing analysis, also called worst-case execution-time (WCET) analysis, to determine such information. key insights the tremendous progress in microprocessor architecture not only increased average-case performance, but also the complexity of verifying the real-time behavior of programs executed on those architectures.to derive useful execution time guarantees, static analyses must prove that speculation mechanisms of modern cPus will indeed be effective during program runtime. this is challenging due to timing anomalies and interdependencies between architectural components. computation takes time, But how much?