>>...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.
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.