Comment by charleslmunger
6 months ago
Very cool. Hardware asan did not catch the pointer provenance bug in the previous implementation of that code because it relies on tag bits, and the produced pointer was bit-identical to the intended one. It sounds like fil-c would have caught it because the pointer capabilities are stored elsewhere.
What hardware do you need for hardware Asan? I'm so out of the loop that I haven't heard of it before.
TBI: https://clang.llvm.org/docs/HardwareAssistedAddressSanitizer...
Thanks!