At some point, someone is going to have to explain why - despite nobody ever wanting this in production code ever, for any reason - the default CSR state for divide by zero on most platforms is fault instead of flush.
-
-
By enabling divide-by-zero exceptions, we effectively take all loops of this form and turn them from perfectly working code to things that literally crash the application :( There are _many_ other forms that look like this, this is just the easiest to type in Twitter.
-
In ASM you can work around some of these. In the previous example, you could presumably move the divide below the top jnz for the for loop, and have the bottom jnz jump back to after the divide, etc., so maybe it "costs you nothing" to do.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
)