Well, the cache is not unlimited, so the unlocked jumps will execute permanently longer (I never understood fully the explanation SiLabs gave for the cache operation but I'd say the penalty is 4 cycles per cache miss).

I mean, only if you have a very very short program where the number of jumps is less than cache positions (where you don't need to lock them then either), the number of cycles - hence consumption per instruction - won't be affected by the fact that the cache needs to be reloaded upon cache miss.


the issue is critical code, who gives a hoot if the initialize code has 4711 cache misses.

This, of course, is ridiculous, but if there was a switch between "SILabs mode" and "traditionsl mode" I guess I could run 90% of my ode in "traditionsl mode" (not that I would).

Erik