It's not a real CPU bug unless you can write a 20 line program in C/assembly and run it to demonstrate the problem. Then, when you've done that, send it to sam

It's not a real CPU bug unless you can write a 20 line program in C/assembly and run it to demonstrate the problem. Then, when you've done that, send it to samsung so they patch it in their CPU design. They may even be able to patch it in their devices in the field (it's common for CPU designs to have special hardware whose purpose is runtime detecting certain trigger conditions and running replacement code to avoid hardware bugs discovered after the CPU was produced). They can also issue an errata which might let compiler authors modify their code generators to avoid any pattern that triggers the bug, therefore avoiding other projects being impacted.