actually, it wasn't a bug; the compiler just optimized a statement away until it was declared volatile. inserting a no-op assembler instruction to make it more obvious what's going on
actually, it wasn't a bug; the compiler just optimized a statement away until it was declared volatile. inserting a no-op assembler instruction to make it more obvious what's going on