Lines Matching refs:speculative

10 vulnerabilities by exploiting speculative execution in modern CPUs. These
21 The core problem of GPZ Variant #1 is that speculative execution uses branch
25 speculative execution is unwound due to being incorrect. Mispredicted paths can
109 though this code pattern may still execute speculatively, *invalid* speculative
130 * It does not completely block speculative execution, and merely prevents
148   non-speculative execution. Code dealing with this, e.g cryptographic
246 speculative store then ends up being used by the CPU during speculative
247 execution of the return, potentially directing speculative execution to
276 speculative, this will often be possible even when these are stored in
311 speculative stores. However, as most stores aren't interesting and don't
557 speculative / out-of-order potential of the execution. There are also several
572 introduce a speculative execution side-channel. This results in code sequences
833 executed. But in that case, the `lfence` cost is a complete loss of speculative
850 fundamentally out-of-order, even in its speculative domain. As a consequence,
920 forming these invalid stack pointer addresses we can prevent speculative
941 We can use this broader barrier to speculative loads executing between
989 region. On Intel systems, `lfence` [will prevent the speculative load of secret