I second that. CPU bugs are the worst you can have. Means that are able to provide insight into instruction space of common CPUs are more valuable then your average particle collider.
The bar is too short for Transmeta and too broad for AMD. It could well be Intel, judging from their other slide using Intel in the same location and font.
Quote from the talk: I don't want to make it sound like the sky is falling. This was found on one very esoteric processor that is not used in widespread production. I think it's mostly interesting from an academic perspective that we have a tool that is able to find these kinds of things now.
For quite a few days, people were suspecting that to be an Intel bug. The desktop shown in the video was a Dell Precision one, which means Core or a Xeon.
Another suspected cpu is said to be Intel X1000, if the demo was not running on the desktop. This was because Intel has issued a non-public errata just for major embedded partners before.
From myself, I will add that another suspect is Intel 80579 which is a still sold Pentium M/Core 1 SoC
While the title is a bit misleading, the presentation suggests enough to say that common CPU designs and architectures should be revised. Undocumented alone should always raise red flags. Imagine your average safe or door lock has undocumented keys or means to be opened without you noticing. Or your car having undocumented extras.
22 comments
[ 6.3 ms ] story [ 59.2 ms ] threadhttps://image.prntscr.com/image/KDuFv8gRQYeLJG3pO8wwmQ.png
Within the context of the prior and subsequent pages, it appears to be talking about AMD.
Besides, a 150+ page document of processor bugs and arcana is hardly FUD.
The bar is too short for Transmeta and too broad for AMD. It could well be Intel, judging from their other slide using Intel in the same location and font.
https://twitter.com/xoreaxeaxeax/status/888702029744324608?l...
https://www.theregister.co.uk/2015/08/11/memory_hole_roots_i...
Quote from the talk: I don't want to make it sound like the sky is falling. This was found on one very esoteric processor that is not used in widespread production. I think it's mostly interesting from an academic perspective that we have a tool that is able to find these kinds of things now.
Sounds like something that would be hopefully fixable in microcode.
For quite a few days, people were suspecting that to be an Intel bug. The desktop shown in the video was a Dell Precision one, which means Core or a Xeon.
Another suspected cpu is said to be Intel X1000, if the demo was not running on the desktop. This was because Intel has issued a non-public errata just for major embedded partners before.
From myself, I will add that another suspect is Intel 80579 which is a still sold Pentium M/Core 1 SoC