3 ms·
Note that more than 1000 errata were released in Intel Core and AMD CPUs in recent years That was predicted: https://news.ycombinator.com/item?id=16058920 http
by userbinator 3y ago
Note that more than 1000 errata were released in Intel Core and AMD CPUs in recent years
That was predicted: https://news.ycombinator.com/item?id=16058920 https://news.ycombinator.com/item?id=16058920
They used to be a bit better than that. IMHO the models released shortly after FDIV bug was discovered would probably have the least errata. Of course, x86 also has a relatively large existing body of software that can exercise obscure instruction sequences --- demoscene productions. I don't know whether they're still using those for testing, however.
As for RISC-V, wasn't one of the biggest selling points of RISC that it would avoid bugs like these due to its reduced complexity in comparison to other architectures? Then again, given that almost all of the bugs found seem to be in the FPU, maybe that's just an inherently complex piece of a CPU.
...and that's before even getting into things like marginal signal integrity/timing, which was the cause of the early 386's 32-bit multiply bug.
- snvzz 3y ago>As for RISC-V, AIUI they only looked at open source implementations. They might not be anywhere as validated as the commercial counterparts. >...and that's before even getting into things like marginal signal integrity/timing, which was the cause of the early 386's 32-bit multiply bug. I'd hope modern fab libraries have checks to prevent these.
- kimixa 3y ago>>...and that's before even getting into things like marginal signal integrity/timing, which was the cause of the early 386's 32-bit multiply bug. >I'd hope modern fab libraries have checks to prevent these. They do - but the end user overclocks the f*ck out of them anyway claiming that it's "stable" because it happens to run one workload OK, then complains about software being unstable.
- sweetjuly 3y ago>As for RISC-V, wasn't one of the biggest selling points of RISC that it would avoid bugs like these due to its reduced complexity in comparison to other architectures? Not really, RISC is about doing what's convenient for HW in HW and leaving other things to SW. It has nothing to do with ease of verification. As the other person mentioned, these are all open source cores, many of which have seen fairly limited DV effort put into them beyond simple lockstep verifiers. The findings here are unfortunately quite shallow and easy to detect issues and so it doesn't give a good sense of the maximum capability of the tool. That being said, it's cool research and better stimulus is always wonderful. Finding deep CPU bugs is extremely hard and verification typically eats up a huge amount of the engineering budget for real chips.