Were it true, the bug would not be discovered the way it was. The arguments of the floating-point operations are not uniformly distributed: you can be fairly certain that a division like -3.094511227530434e+272 / 1.6897234923591976e+193 was never encountered in the history of mankind, unlike 4195835.0 / 3145727.0 or 4.999999 / 14.999999, both of which happen to trigger the bug (and, of course, ones like 2.0 / 5.0 are even more common).
Also, much of the backslash received by Intel over the bug was caused by them first not publishing an errata, despite being aware of the problem for 6 months before it went public, and then attempting to dismiss it by bullshit like the above statistics.
Copyright © 2018, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds