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 :(
That _should_ be considered unacceptable, in my opinion, for any project where speed is a concern. So if you were, for example, caring about the speed of your hash function in the first place, you should be considering ASAN not ready for prime time.
-
-
In the future, masked loads that don't fault off the page will be literally everywhere - it's literally the instruction everyone will have to call when doing loads on AVX-512. So what then?
-
It isn't clear to me if you are talking about multi-instruction masking idioms like "load this, AND away some bytes" or actual all-in-one masked instructions like vmaskmov. I 100% agree the latter should not be flagged by ASAN if the included portion of the read is in-bounds.
- 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.