3 ms·

Can you really call "fast but wrong/insecure" optimized?

• mark-r 8y ago
  Yes you can, if it makes your benchmarks look better. That's why Intel is trying to suppress the benchmarks.
• Dylan16807 8y ago
  It doesn't calculate anything wrong, so sure. For this particular optimization, it looks better not to have it. But in general, knowing how something is flawed lets you mitigate the flaws. We use floating point despite it being mathematically wrong, because it's fast and we can mitigate the wrongness. I could imagine a chip where speculation could be toggled between different modes, if there was enough demand. I will say that "just further behind" is probably wrong. AMD has a lot of optimizations in their chips. They have safer ones, which might be luck or might be engineering talent, but it's not a mere artifact of being behind the curve.