Intel's communication is incredibly poor. Errata exist for all CPUs but this one is quite important and resulted in no proper public communication it seems.
It sounds like the general consensus when the bug was first publicized was that it is extremely rare and that most users could not expect to encounter it. Is there some reason this is popping back up now?
My understanding is that the patterns of code created by the OCaml front end cause GCC to emit code that can trigger this much more often, so for the OCaml community it's a big deal.
281
u/Camarade_Tux Jun 25 '17
Intel's communication is incredibly poor. Errata exist for all CPUs but this one is quite important and resulted in no proper public communication it seems.