On Fri, Dec 6, 2013 at 3:28 PM, Yury Gribov <y.gri...@samsung.com> wrote: > Hi all, > > GCC version of Asan currently lacks options for detailed control over code > instrumentation. These are not usually necessary but for embedded systems > with scarce system resources Asan memory overhead of 2x-3x may often be > unacceptable.
my 2c: only -asan-stack and -asan-globals affect the memory overhead, others don't. The blacklist functionality may potentially be useful for gcc-asan users, the clang variant is documented here: http://clang.llvm.org/docs/SanitizerSpecialCaseList.html > > It seems that LLVM provides some options to allow programmer select which > part of his code/memory he's interested in: > * -asan-instrument-reads > * -asan-instrument-writes > * -asan-memintrin > * -asan-stack > * -asan-globals > * -blacklist > These options allow one to selectively turn on Asan for separate parts of > code / classes of memory thus reducing the net overhead. > > Would GCC community be interested of similiar functionality? We could start > with implementing above options in 4.9. > > -Y > > >
