This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: RFC Asan instrumentation control
- From: OndÅej BÃlka <neleai at seznam dot cz>
- 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 12:42:19 +0100
- Subject: Re: RFC Asan instrumentation control
- Authentication-results: sourceware.org; auth=none
- References: <52A1B4F2 dot 8040105 at samsung dot com>
On Fri, Dec 06, 2013 at 03:28:50PM +0400, Yury Gribov 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.
>
This is implementation detail and may be gone with more effective
implementation of shadow memory. Then patch to add these may cease to be
usefull.
> 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.
>