This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: RFC Asan instrumentation control
- From: Konstantin Serebryany <konstantin dot s dot serebryany at gmail dot com>
- To: Yury Gribov <y dot gribov at samsung dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, Viacheslav Garbuzov <v dot garbuzov at samsung dot com>, Max Ostapenko <m dot ostapenko at partner dot samsung dot com>
- Date: Fri, 6 Dec 2013 15:44:30 +0400
- Subject: Re: RFC Asan instrumentation control
- Authentication-results: sourceware.org; auth=none
- References: <52A1B4F2 dot 8040105 at samsung dot com>
On Fri, Dec 6, 2013 at 3:28 PM, Yury Gribov <y.gribov@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
>
>
>