[libre-riscv-dev] [Bug 206] Implement branch prediction

bugzilla-daemon at libre-riscv.org bugzilla-daemon at libre-riscv.org
Mon Mar 2 21:39:39 GMT 2020


--- Comment #2 from Luke Kenneth Casson Leighton <lkcl at lkcl.net> ---
(In reply to Jacob Lifshay from comment #0)

> To avoid spectre-style data leaks where feasible, we should only send
> taken/not-taken data back to the branch predictor once all preceding
> branches are no longer speculative (tracked by dependency matrix).

that's going to be interesting.  all *preceding* branches.  do they
mean branches that are in play whilst *other* branches are still in play?
double-shadowing, in other words?

You are receiving this mail because:
You are on the CC list for the bug.

More information about the libre-riscv-dev mailing list