It's definitely better than completely giving up on speculation, although I believe that was a necessary first step. The approach of putting in speculation barriers seems kinda naive though given the amount of understanding the average dev has even of memory barriers.
Here "changing the ISA" means "declaring all existing binaries AND TOOLING for the old ISA deprecated and unusable".
-
-
Could you be specific about what breaks? For most machines in the world only the browser's JIT engine needs a change. For virtualized servers the hypervisor.
-
That's really naive. An interpreter/JIT running hostile code is the most obvious way to exploit Spectre but there's no guarantee it's the only one.
-
I strongly suspect there will be ways to exploit via specially crafted files thought of as "pure data".
End of conversation
New conversation -
-
-
If the solution for a given ISA (let's say x86_64) is to add an incompatible ISA requirement that you use explicit speculation barriers, that basically says "the only compilers you can use are bleeding-edge GCC, clang, MSVC(?), and icc".
-
I'm not denying there are other chains out there. I've just not seen them.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.