Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

There's explicit speculation barriers that they document, but they don't tell you what _other_ instructions are speculation barriers simply due to microarchitectural compromises like what you're seeing in this article.


OK thanks for clarifying. If there are explicit instructions for blocking speculation then why are you concerned about implicit barriers?


I'm not. My point is that this article was being unfairly interpreted by the parent as some black mark against x86. There's plenty to hold against it, but not really anything that's documented here. I probably should have made that clearer.


Seems like implicit undocumented barriers could be used in critical code to provide unfair performance advantage. Maybe. Might be a bit of a stretch.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: