4 ms·
I don't understand how this fix can possibly be so performant. The speculative executions must be doing something positive, right? It seems like it should nev
by x0x0 9y ago
I don't understand how this fix can possibly be so performant. The speculative executions must be doing something positive, right? It seems like it should never hurt (ignoring security, obv). So how can disabling it not hurt?
Thanks for the stackover flow link!
- bradleyjkemp 9y agoSounds like they're just forcing the CPU to use a different (less vulnerable) type of predictor. It's the branch target predictor that's vulnerable so instead of using a branch instruction the compiler now adds a mini stack frame (with the return address as the place we want to jump to) and then "returns". The CPU now happily predicts the target using the non-vulnerable stack predictor and does do speculative execution.