I wish ASAN understood memory page boundaries and masked reads, because it sucks getting people telling you your code fails under ASAN when in fact it is correct code and you have to explain that it is that way on purpose :(
-
-
I'm very much in two minds about this. Reading off the end of a buffer is UB, and while I'm not one of those people who runs around with my dress over my head yelling "UB! UB!" it doesn't seem 100% kosher either. I also don't like the idea of breaking valgrind/asan for other ...
-
... people running my library. If someone wants to, they can structure their code to be 100% green lights with these tools, but if my library breaks that, they enter the fun world of "oh, we're 100% compliant aside from this weird ding from those Hyperscan folks". I'm not in ..
- Show replies
New conversation -
-
-
I guess this stems from their conclusions made looking at the software hacked around to make it work, and businesses. Got to make it future proof, as the history is cyclic and your computers will turn into pumpkins overnight, now running on seednary arithmetic.
-
Some concerns are legitimate, like using the high bits for tagged pointers (this assumption can break already on x64). On to handholding they go, instead of providing the evidence for the dangers, and suggesting that maybe you'll do fine with only the lowest bits.
- 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.