Details
Details
- Reviewers
kcc
Diff Detail
Diff Detail
Event Timeline
Comment Actions
The code looks fine, please just add a test to llvm/test/Instrumentation/AddressSanitizer/instrumentation-with-call-threshold.ll
I actually considered to always emit calls for non 1-, 2-, 4-, -8, and 16-byte accesses to simplify the code and testing.
This will slowdown this use case somewhat, but those accesses are extremely rare anyway.
What do others think?
Comment Actions
AVX access are power of two, right?
As soon as we get a hardware where we can test AVX, we'll add 32- and 64-byte accesses. They should not be instrumented with __asan_loadN