Приклади вживання Speculative execution Англійська мовою та їх переклад на Українською
{-}
-
Colloquial
-
Ecclesiastic
-
Computer
Dynamic schemes for speculative execution of code.
But speculative execution, as a technique, is simply far too valuable to stop using.
Branch prediction is used with speculative execution.
Speculative execution is a technique CPU designers use to improve CPU performance.
Spectre andMeltdown target some core features of modern CPU known as speculative execution.
Speculative execution has been in the news of late, typically when discussing the Meltdown and Spectre bugs.
This can potentially give rise to a speculative execution side channel and the disclosure of sensitive information.
Speculative execution is an optimization technique where a computer system performs some task that may not be needed.
It's not clear if theycan ever be resolved without jettisoning speculative execution, and the tremendous performance benefits it delivers.
And speculative execution, while implemented differently from company to company, is used by each of them.
Spectre targets a feature of microprocessors called speculative execution, which performs calculations that may be needed ahead of time.
Meltdown and Spectre are so dangerous because they affect one of the mostimportant low-level features of CPUs known as speculative execution.
Code that's running under speculative execution doesn't do the check whether or not memory accesses from cache are accessing privileged memory.
The L2 cache is multi-versioned, supporting transactional memory and speculative execution, and has hardware support for atomic operations.
Speculative execution which allow the execution of complete instructions or parts of instructions before being sure whether this execution is required.
As we have previously discussed,this attack again targets an aspect of speculative execution- in this case, it's called a Speculative Store Bypass(SSB).
Speculative execution which allows the execution of complete instructions or parts of instructions before being certain whether this execution should take place.
Because the original attack identified an entireclass of methods of attacking CPUs that engage in speculative execution, we could be dealing with this problem for years to come.
As discussion of the Spectre and Meltdown bugs dominates the tech news cycle,there's been repeated reference to a specific feature of high-end CPUs: speculative execution.
Features like L1, L2, and L3 caches and speculative execution were designed to keep the CPU busy and minimize the time it spent idling.
Other aspects of these CPUs remain entirely unknown,including any question of architectural enhancements or additional hardware fixes for the speculative execution issues that continue to surface.
Here's what speculative execution is and how it relates to other key capabilities of modern microprocessors, and how the recent Meltdown bug targets Intel CPUs in particular.
When Spectre was originally discovered, researchers feared the only way tomitigate it would be to disable CPU's“speculative execution” features, which allow CPUs to work ahead and do calculations that may be needed in the future.
Speculative execution helps processors predict to a certain degree what an application or operating system might need next and in the near-future, making the app run faster and more efficient.
There are differences between how Intel, AMD, and ARM implement speculative execution, and those differences are part of why Intel is exposed on Meltdown in ways that the other vendors aren't.
While speculative execution is a longstanding and proven technique for improving overall CPU performance, de Raadt identifies three distinct issues that have combined to create these problems. He writes:.
As has been the case with previous Spectre attacks,this new variant targets the behavior of microprocessors engaged in speculative execution, or the practice of performing calculations that may nor may not be actually used as a means of improving overall performance.
Several other forms of speculative execution have been proposed andare in use including speculative execution driven by value prediction, memory dependence prediction and cache latency prediction.
Without branch prediction and speculative execution, the CPU doesn't know which branch it will take until the first instruction in the pipeline(the green box) finishes executing and moves to Stage 4.