WCET analysis (was: Privilege Levels Below User)

Not always. If the mistakenly speculated cache-fetch /evicted/ some other
data from the (finite-sized) cache, and the evicted data are needed later on
the /true/ execution path, the mistakenly speculated fetch has a /negative/
effect on performance. (This kind of "timing anomaly" is very bothersome in
static WCET analysis.)

BTW, I heard that nowadays "static WCET analysis" is typically based on
statistical models of the performance of various parts of the code.
So they don't give an ironclad worst case any more (contrary to what
you'd get back in the day where you could count cycles and there were no
caches), but rather one that is "very unlikely" to be wrong.

I remember papers doing "real WCET" by analyzing the code to detect
those memory accesses which were guaranteed to be cache hits.  Do you
know if this is still done nowadays?


        Stefan