You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 11, 2020. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.The text was updated successfully, but these errors were encountered: