I think you are glossing over a lot of complexity in > 4. Correctly run several software unit tests that you write to exercise instructions that may not be pro

I think you are glossing over a lot of complexity in > 4. Correctly run several software unit tests that you write to exercise instructions that may not be produced by LLVM/GCC and > 5. Correctly run tests you write to exercise specific processor/cache states These two alone seem like they could be really quite complicated. Also, "run the world" is pretty slow when you have to do it in simulation (or emulation if you wait to have a netlist to find out how broken it is). I suspect the coverage from your list is substantially lower than you might expect. Would this have caught F00F? FDIV? AMD Phenom's TLB bug?