News for hackers. Stuff that matters.
Re:Debugging an evil Go runtime bug by cwzwarich on Monday December 04, 2017 @02:22PM (#15846626)
Why is it shorter? Both MOV and OR have one byte encodings, and with the OR you either have to use an immediate zero (which burns a byte) or materialize zero in some other way. As that email points out, the entire sequence would be shorter using a different addressing mode anyways. And a read-modify-write is definitely slower at runtime.
Re:Debugging an evil Go runtime bug by simcop2387 on Monday December 04, 2017 @04:31PM (#15847706)
I wonder if it's because it's safer in that it doesn't change anything there if you've gone over the stack limit and into the heap? I know that -fstack-protect was designed a long time ago, possible before guard pages and before 64bit addressing.