Skip to content
This repository has been archived by the owner on May 11, 2020. It is now read-only.

Analyze spectre implications #130

Open
twitchyliquid64 opened this issue Jun 7, 2019 · 0 comments
Open

Analyze spectre implications #130

twitchyliquid64 opened this issue Jun 7, 2019 · 0 comments

Comments

@twitchyliquid64
Copy link
Contributor

twitchyliquid64 commented Jun 7, 2019

No work has been done to determine if the interpreter/bytecode-dispatch loop is vulnerable to spectre, nor am I confident that mitigations applied for memory load in the native compiler are fully effective.

We should sit down and work out for sure if there is any more work to do here.

My gut feeling is that the dispatch loop has sufficiently high overhead that mis-speculating through incorrect instructions is infeasible. I'm more concerned about I64Load/I32Load in the native compiler, it would be nice to have a test that demonstrates they mitigate spectre.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant